ResumeQuick

Delete an archived job

delete_vacancy

Destructive

Permanently delete an ARCHIVED vacancy. Irreversible — the vacancy and its history are gone, and a linked tailored resume, interview or offer survives with its link cleared, and the radar match it came from is deleted too and not offered again (the response counts them). Returns 'not_archived' if the vacancy is still active: archive it first with archive_vacancy, which is what the user usually means by 'remove it'. Returns 'not_found' if it does not exist or does not belong to the current user. Consumes no quota and refunds none.

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description
`id`	Yes
`deleted`	No
`offers_unlinked`	No	Offer negotiations that lose their link.
`interviews_unlinked`	No	Mock interviews that lose their link.
`reminders_cancelled`	No	Pending reminders cancelled with the vacancy.
`radar_matches_deleted`	No	Radar matches that pointed at this analysis; deleted with it, a later scan does not bring them back.
`tailored_resumes_unlinked`	No	Tailored resumes that survive but lose their link to this vacancy.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026

removedOutput schema / properties / radar_matches_archived

Removed value: -{
-  "default": 0,
-  "description": "Radar matches that pointed at this analysis and were moved to the radar archive, not deleted.",
-  "title": "Radar Matches Archived",
-  "type": "integer"
-}

addedOutput schema / properties / radar_matches_deleted

Added value: +{
+  "default": 0,
+  "description": "Radar matches that pointed at this analysis; deleted with it, a later scan does not bring them back.",
+  "title": "Radar Matches Deleted",
+  "type": "integer"
+}

First observedOct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes further: it discloses irreversibility, the cascade semantics (linked resume/interview/offer survives with link cleared, radar match deleted and never re-offered), and quota behavior. That is behavioral context an agent cannot get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the destructive action and precondition, then cascades, then error codes. Dense and every sentence carries information, though the cascade clause is a long compound sentence that could be split for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still names the meaningful return codes and side-effect counts, so nothing an agent needs to call this correctly or interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter and the schema's own description is thin, but the tool description reinforces the key constraint (it must be an ARCHIVED vacancy) and explains what 'not_found' implies about ownership. Good compensation for the low schema coverage, though it doesn't discuss id formats.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Permanently delete') plus resource ('ARCHIVED vacancy') and its precondition, and immediately distinguishes itself from archive_vacancy and the other delete_* siblings. The uppercase ARCHIVED makes the scope unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use (only archived vacancies), when-not, and the alternative ('archive it first with archive_vacancy, which is what the user usually means by "remove it"'). Error routing ('not_archived', 'not_found') tells the agent exactly what to do next on failure.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ResumeQuick tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.