Skip to main content
Glama

Manage my resume versions

manageResumeVersions
Destructive

Create, rename, delete or switch the default of the candidate's resume-builder versions, the same as the versions menu on the dashboard resume page. create makes an empty version, or a copy of draftId; rename and make_default take draftId and, for rename, name; delete removes a version that isn't the default, together with its PDF. Take draftIds from readResumeDraft. The default version is what readResumeDraft, editResumeDraft and generateResumePdf use when no draftId is passed. Confirm a delete with the candidate first.

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": {
      "action": "<action>"
    },
    "name": "manageResumeVersions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNocreate and rename: the version's name, up to 60 characters.
actionYes
draftIdNoThe version to act on, from readResumeDraft drafts. Required for rename, make_default and delete; with create, the version to copy.

Output Schema

NameRequiredDescriptionDefault
actionYes
draftsYes
draftIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by naming exactly what is destroyed on delete (the version plus its PDF), the constraint that the default cannot be deleted, and how the default affects readResumeDraft/editResumeDraft/generateResumePdf. It also adds a safety instruction to confirm deletes with the candidate and a privacy/data-tracking note, none of which the annotations carry.

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-loads the verb list, then walks the actions in order, ending with the default-version semantics that explain why the tool matters. Dense but every clause carries information; the trailing privacy sentence is boilerplate but brief.

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?

A destructive multi-action tool with 3 params, an output schema, and full annotation coverage; the description supplies the destructive scope, default-version coupling, and cross-tool sourcing needed to call it safely. Nothing an agent needs to invoke or sequence it correctly 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 coverage is 67% and the schema already documents name length and draftId sourcing, so the description's value is in mapping parameters to actions (which action requires name vs. draftId). That conditional mapping is the key added meaning; it does not add format or validation detail beyond the schema.

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 set and resource: "Create, rename, delete or switch the default of the candidate's resume-builder versions," and anchors it to a known UI surface (the versions menu). Each action is then defined, so an agent can distinguish this from readResumeDraft/editResumeDraft 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?

Gives clear per-action context: create makes an empty version or a copy of draftId, rename/make_default take draftId, delete only works on non-default versions, and draftIds come from readResumeDraft. It also explains what the default means for downstream tools. It stops short of explicit exclusions (e.g., when to edit a draft instead of creating a new version).

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