Skip to main content
Glama

Delete a resume

deleteResume
DestructiveIdempotent

Remove one of the candidate's resumes from their list. Clera archives it: it stops going to companies and stops feeding the profile, and the Clera team can restore it. Removing the primary makes their newest remaining resume primary; removing the last one leaves them with none. Confirm with the candidate before calling.

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": {
      "resumeId": "<resumeId>"
    },
    "name": "deleteResume"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeIdYesThe resumeId from listResumes.

Output Schema

NameRequiredDescriptionDefault
nameYes
resumeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds real substance: the record is archived rather than purged, it stops flowing to companies and stops feeding the profile, Clera can restore it, and inputs/results are recorded. The only notable omission is that primary resume reassignment is described but not whether in-flight applications are affected.

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?

It is front-loaded with the action, then the consequences, then the confirmation requirement, with no wasted clauses. The trailing data-recording sentence is boilerplate but short and arguably a required disclosure, so it costs little.

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

Completeness4/5

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

For a single-parameter destructive tool with an output schema and rich annotations, the description covers the cascade effects, reversibility, and the confirm-first rule. Nothing critical for a correct call is missing, though it could say what happens to resumes already attached to applications.

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?

With a single parameter and 100% schema description coverage, the schema already tells the agent to use the resumeId from listResumes. The description adds no format, sourcing, or error semantics beyond that, so the baseline of 3 applies.

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

Purpose4/5

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

"Remove one of the candidate's resumes from their list" gives a specific verb (remove) and a specific resource (a resume in the candidate's list), which an agent can distinguish from deleteTailoredResume-type operations. It stops short of naming a sibling to contrast with, so the differentiation is inferred rather than stated.

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 supplies a concrete precondition before invocation: "Confirm with the candidate before calling." That is actionable workflow context, but there is no explicit exclusion or comparison against the other delete* resume tools, so an agent must still reason about which delete to pick.

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