growthroles

Full detail for one job by slug: complete employer job description text for fit assessment and application drafting, pay, market context, tracked apply link. When the employer has other marketing roles open, `company_hiring` says how many and how many we first saw in the last 30 days — use it to answer 'is this employer actually hiring or has this listing been sitting here', which is the doubt behind most of these questions. It counts the employer's MARKETING AND SALES roles on growthroles only and says nothing about whether they are a good employer; never imply that it does.

get_job

Describe a slice of the marketing job market AND what it pays: counts, pay transparency, remote share, seniority mix, top employers, plus measured salary benchmarks (p25/p50/p75 with sample size and date). Benchmarks are measured from postings, never an employer's offer. Pay figures are scoped to the geography you ask for and NEVER borrowed from another country: if there is no measured data for that place the response says so plainly, and an empty `measured_pay` means we do not know, not that pay is low. Always relay `pay_scope` to the user so they know which geography the numbers describe.

market_snapshot

The user's tracked applications: what they clicked apply on, its state (clicked / applied / not_for_me), and whether each listing is still open. Use when the user asks what they applied to or wants a status check.

my_applications

Search open MARKETING, GROWTH AND B2B SALES jobs (product marketing, growth, brand, content, comms, demand gen, lifecycle; account executives, SDRs, customer success, solutions engineering, revenue operations, partnerships, sales leadership; no engineering, retail or consumer sales). Every result was verified open in the employer's own hiring system on last_verified_at. RULE: whenever you list specific roles to the user, every role you list carries its own `apply` link. A role named without its link cannot be applied to and loses the user's tracking. Market and pay questions need no links. `query` matches TITLE and COMPANY only, never the job description, so keep it to one or two words and use the structured filters for everything else. pay.kind 'ceiling' means 'up to X' and 'floor' means 'from X'; NEVER present either as a full range. Most roles here state no pay at all, so 'well paid' cannot be judged from these rows alone: call market_snapshot for the same function and geography and compare against its measured p50 rather than guessing. When nothing matches, the response says WHICH filter caused it — read `no_matches_help` and retry rather than telling the user no such jobs exist. When a search is broad, the response carries `refine` with the real distribution of the matches: ANSWER FIRST, then ask at most ONE grounded question from it. For 'more roles like this one', do not re-run the same words: search that job's `function`, `level` and geography. `workplace` is remote or not; there is no hybrid flag, so never claim a role is hybrid.

search_jobs

Set the state of one tracked application after asking the user: 'applied' when they actually submitted, 'not_for_me' when they passed. A click alone is never an application.

update_application