Skip to main content
Glama

update_resume

Save edits onto an existing resume. Pass the version from the latest get_resume, create_resume, or duplicate_resume response in this turn. On resume_invalid, fix validation and retry with the same version. On resume_conflict, call get_resume again. The server owns id, source, createdAt, updatedAt, openedAt, jobTitle, and the tailoring object. To set the company the job is at, pass company and, when you know the company website, companyDomain; leave both out to keep the stored company. company or companyDomain inside the document body is ignored. A bad value returns invalid_input.

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>",
      "version": "<version>",
      "resume": "<resume>"
    },
    "name": "update_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeYes
companyNoThe company the job is at, at most 200 characters. An empty string removes the company and its domain.
versionYes
resumeIdYes
companyDomainNoThe company website as a bare hostname, such as lucid.co (no https://, path or port). Sets the logo. Needs company.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses which fields the server owns and will not accept from the caller (id, source, timestamps, jobTitle, tailoring), that company or companyDomain inside the document body is ignored, and the error contract (resume_invalid, resume_conflict, invalid_input). This is exactly the mutation-specific context annotations cannot convey.

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 core action and follow-up guidance, and every sentence carries operational content. The density of error codes and field names makes it slightly scan-heavy, but there is no filler.

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 mutation tool with a free-form nested body and no output schema, the definition covers versioning, server-owned fields, error recovery, and company precedence well. The remaining gap is what a successful response contains (whether a new version is returned), which the agent must infer.

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?

At 40% schema coverage, the description meaningfully supplements version (where the value must come from) and clarifies company/companyDomain precedence over the document body, but resumeId is never explained and the resume object — a free-form nested payload — has no structural guidance beyond the negative rule that company fields inside it are ignored.

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?

"Save edits onto an existing resume" gives a specific verb and resource, and the word "existing" distinguishes it from create_resume and duplicate_resume. The mention that the version comes from get_resume, create_resume, or duplicate_resume further situates it in the sibling workflow.

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?

It states the prerequisite sequencing (pass the version from the latest get_resume/create_resume/duplicate_resume response in this turn) and prescribes exact recovery paths: fix validation and retry with the same version on resume_invalid, call get_resume again on resume_conflict. Company fields have an explicit include/exclude rule (leave both out to keep the stored company).

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