Skip to main content
Glama

Delete an archived job

delete_vacancy
Destructive

Delete an ARCHIVED vacancy. The vacancy and its history leave the user's lists at once and are erased for good a day later; until then the web app's Undo brings it back, and no tool here does. The tailored resume made for it goes with it when that copy is not the active resume and the vacancy is still at status new; otherwise 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "delete_vacancy"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
idYes
deletedNo
offers_unlinkedNoOffer negotiations that lose their link.
interviews_unlinkedNoMock interviews that lose their link.
reminders_cancelledNoPending reminders cancelled with the vacancy.
radar_matches_deletedNoRadar matches that pointed at this analysis; deleted with it, a later scan does not bring them back.
tailored_resumes_deletedNoInactive tailored copies made for this vacancy, deleted with it because it was still at status new.
tailored_resumes_unlinkedNoTailored resumes that survive but lose their link to this vacancy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $defs / DeleteVacancyInput / properties / vacancy_id / description
      Previous value: -"Id of the ARCHIVED vacancy analysis to delete permanently."New value: +"Id of the ARCHIVED vacancy analysis to delete."
    • addedOutput schema / properties / tailored_resumes_deleted
      Added value: +{
      +  "default": 0,
      +  "description": "Inactive tailored copies made for this vacancy, deleted with it because it was still at status new.",
      +  "title": "Tailored Resumes Deleted",
      +  "type": "integer"
      +}
  2. Changed2 schema fields changed
    • 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"
      +}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes far beyond the destructiveHint=true / idempotentHint=false annotations: it discloses the two-stage lifecycle (leaves lists now, erased for good a day later), that the web app's Undo exists but no tool does, the exact cascade rules for tailored resumes, interviews, offers, and radar matches, and that the radar match is not offered again. Quota behavior is also stated. This is unusually complete behavioral disclosure for a destructive tool.

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 action and precondition, then cascades, then error codes, then quota. Dense but every clause carries operational information. Slightly long sentences (the resume/radar-match cascade clause) cost it a point on readability, not on relevance.

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?

For a destructive, cascade-triggering tool with a single parameter and an output schema, the description covers preconditions, side effects, error returns, and recoverability. Nothing an agent needs before calling it is missing, despite the output schema already handling return shape.

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

Parameters5/5

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

Schema coverage is reported as 0%, so the description must carry the parameter meaning, and it does: it constrains vacancy_id to an ARCHIVED vacancy and defines the two failure semantics (not_archived, not_found including the 'does not belong to the current user' case) that determine what a valid id actually is.

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?

Opens with a specific verb+resource+precondition: 'Delete an ARCHIVED vacancy.' The all-caps ARCHIVED immediately distinguishes it from sibling archive_vacancy and from generic deletion, so an agent can route correctly without opening either schema.

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?

Explicitly states when not to use it ('Returns not_archived if the vacancy is still active: archive it first with archive_vacancy') and even notes that archiving 'is what the user usually means by remove it', which is exactly the disambiguation an agent needs. Names the alternative tool directly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.