Skip to main content
Glama

AceRound AI Interview Copilot

delete_resume

Destructive

Delete one of the user's resumes. Resume ids come from list_resumes. Deletion cannot be undone; tell the user what will be deleted and get their agreement first. (Requires the user's sign-in with scope resumes:write.)

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": "delete_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Although annotations already flag destructiveHint=true and readOnlyHint=false, the description adds material context beyond them: the deletion is irreversible, the agent must tell the user what will be deleted and obtain agreement, and the call requires the resumes:write auth scope. These are exactly the operational facts an agent needs before invoking a destructive mutation.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and scoped by the id source, then the risk warning and the auth requirement. Every sentence carries distinct, non-redundant information with no filler.

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 single-parameter destructive tool with no output schema, the definition covers what it does, where the id comes from, that the effect is permanent, the confirmation workflow, and the required auth scope. Nothing an agent needs in order to call it safely 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?

Schema description coverage is 0%, so the schema supplies only type and length constraints with no meaning. The description compensates by explaining that resumeId values come from list_resumes, which is the key semantic detail; it does not add format or edge-case notes (e.g., what happens with an unknown or already-deleted id), keeping it just below a 5.

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 of the user's resumes") and immediately clarifies scope so it is distinguishable from sibling resume tools such as get_resume, list_resumes, and upload_resume. It also states where the identifier originates, removing ambiguity about what the single parameter refers to.

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?

The definition gives clear usage context: obtain the id from list_resumes, and confirm with the user before proceeding. It stops short of naming an explicit alternative or when-not-to-use condition (for example, whether a resume can be replaced or archived instead), so it is strong but not exhaustive.

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