What job post management covers
list_job_posts shows every job you have, draft, published, or closed, with status and applicant count, useful before drafting anything new so you're not creating a near-duplicate of a role that already exists, or forgetting a draft that's been sitting unfinished for weeks. create_job_post drafts a new post and always leaves it in draft status, regardless of how the request is phrased.
update_job_post changes fields on an existing post you name, title, description, location, salary, requirements, without touching its publish status, so a mid-flight correction never accidentally takes a draft live or a live post down.
publish_job_post and pause_job_post are the two status-change tools, putting a draft live or taking a published post down, each its own approval and each restricted to jobs in the right state to begin with.
benchmark_job compares a role against your own applicant volume and average score, and against real current market pay for that role and location, giving a number to weigh against instead of a guess at whether a salary figure is actually competitive.
A walkthrough: posting a role with a sanity check first
An employer says: "draft a job post for a senior backend engineer in Austin, and check if 155k is competitive." The agent calls list_job_posts first, confirms no near-duplicate exists, drafts the post, and shows an approval card: "Create draft job 'Senior Backend Engineer'?"
Once approved, it runs benchmark_job and reports back that 155k sits slightly under the current market range for that role and location, with the employer's own similar roles pulling a strong average applicant score at a higher figure. The employer bumps it to 165k, asks the agent to update the draft, and once that's confirmed, says publish it.
A final, separate approval card appears: "Publish job 'Senior Backend Engineer' to the public board?" Only after that confirmation does the role actually appear where candidates can see and apply to it.
Boundaries
What publishing always requires separately
A newly created job post is always a draft, with no path for create_job_post itself to publish it, no matter how the request is phrased. Publishing and pausing each require their own approval card and only apply to a job already in the right state, published jobs can't be re-drafted through this tool and draft jobs can't be paused since they were never live in the first place.
benchmark_job never changes anything, it only reads your applicant data and public market figures side by side, so it's safe to run at any point in the drafting process without affecting the post itself.
list_job_posts is read-only too, which is why the agent is expected to reach for it early and often, before drafting, before benchmarking, and before publishing, without any of those checks ever counting against your approval budget for the day.
Frequently asked questions
If I ask the agent to draft and publish a job post in one request, does it go live immediately?
No. Creating a job post always saves it as a draft first. Publishing is a separate, separately-approved step, even if you asked for both actions in the same message.
Can the agent tell me if a job's salary is competitive?
Yes, benchmark_job compares the role against your own applicant data and against real current public market salary information for that role and location.
Can I take a job post down without deleting it?
Yes, pause_job_post removes a published job from the public board. It only works on jobs that are currently published.
Does the agent check for duplicate job posts before drafting a new one?
It's expected to check list_job_posts first, showing what already exists so a new draft doesn't duplicate a role you've already posted.
Can I update a job's description without accidentally taking it offline?
Yes, update_job_post changes fields like description, salary, or requirements without touching the job's publish status, so an edit never quietly pauses or publishes it as a side effect.
Related pages
Draft a role with a benchmark attached
Ask the agent to draft the post, check it against real market pay, then approve publishing once it looks right.