Skip to main content
Glama

Delete a tailored resume

deleteTailoredResume
DestructiveIdempotent

Delete one tailored resume and its PDF for good. The tracked application stays, and applyToJob goes back to sending the candidate's primary resume for that job. Confirm with the candidate before calling; there is no undo, though generateApplicationDocuments can write a new one.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "draftId": "<draftId>"
    },
    "name": "deleteTailoredResume"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYesThe draftId from listTailoredResumes or getTailoredResume.

Output Schema

NameRequiredDescriptionDefault
nameYes
draftIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description goes well beyond them: it says the application record is preserved, that applyToJob reverts to the primary resume, that there is no undo, and that a confirmation step is required. It even discloses a Cleva-specific data-logging practice, which is real behavioral context an agent cannot get from structured fields.

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?

The primary sentence front-loads the mutation, its side effects, and the safety requirement, and the second sentence covers recovery. The trailing privacy/logging sentence is boilerplate but does carry disclosure value; without it the definition would be tighter.

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 single-parameter tool with annotations and an output schema present, everything an agent needs is covered: what is destroyed, what persists, downstream consequences, required confirmation, and reversibility. Nothing material is left to inference.

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

Parameters3/5

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

The single parameter draftId has 100% schema description coverage that already explains its origin ('The draftId from listTailoredResumes or getTailoredResume'). The description adds nothing about the identifier's format or validation, so the baseline 3 for a fully documented schema applies.

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?

The description opens with a specific verb and resource — 'Delete one tailored resume and its PDF for good' — and immediately scopes the blast radius by naming what survives ('The tracked application stays'). It also names real siblings (applyToJob, generateApplicationDocuments), so the agent can distinguish this from adjacent delete/generate tools without opening a schema.

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

Usage Guidelines4/5

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

It gives an explicit precondition ('Confirm with the candidate before calling') and a recovery path ('generateApplicationDocuments can write a new one'), which is genuine when-to-use guidance. It stops short of a full when-to-use/when-not-to-use routing rule, leaving the choice against other delete variants implicit, so it is one notch below the top.

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.

Resources