Skip to main content
Glama

Edit the tailored resume

update_resume
Idempotent

Use this when the user asks to change a tailored resume: exact text edits, additions or removals based on what the user said, or the template, palette, font or density. Creates a new revision from the latest operationId, without AI or another adaptation; earlier revisions stay available to undo. For content edits, userRequest must quote the user's request; never add a fact the user did not state. Do not use to tailor the resume to another job; use create_tailored_resume.

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": {
      "guestToken": "<guestToken>",
      "operationId": "<operationId>"
    },
    "name": "update_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
editsNo
appearanceNo
guestTokenYes
templateIdNo
operationIdYes
userRequestNo

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
statusYes
recoveryNo
downloadUrlNo
operationIdYes
expiresInSecondsNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true; the description adds the non-obvious revision model — a new revision is created from the latest operationId, no AI/adaptation occurs, and prior revisions stay available to undo. It also imposes a substantive constraint: 'never add a fact the user did not state'. It does not cover guestToken/auth requirements or failure behavior, so it stops short of a 5.

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?

Three sentences, front-loaded with the use case, followed by behavior, followed by the exclusion — a logical order with no filler. The behavior sentence is dense, packing revision semantics, the no-AI note, undo availability and the userRequest constraint into one clause chain, which costs a little readability.

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?

An output schema exists, so return values need no explanation, and the description covers both editing modes plus the exclusion for a complex nested-schema tool. The remaining gap is the undocumented required guestToken and the absence of any hint about how edits reference fields, which matters given a 6-parameter, nested-object schema.

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?

Schema description coverage is 0%, so the description must carry the burden, and it does explain the semantic role of operationId (must be the latest revision) and userRequest (must quote the user verbatim). However, the required guestToken parameter is never mentioned, and the edits array shape (path/action/value, append-by-index) is only hinted at by 'exact text edits, additions or removals'.

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 trigger and verb: 'change a tailored resume', then enumerates the two edit classes (content edits vs. appearance/template). It explicitly names what it is not: 'Do not use to tailor the resume to another job; use create_tailored_resume', separating it from the closest sibling without requiring a schema open.

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 gives positive selection criteria (exact text edits, additions/removals, or template/palette/font/density changes) and an explicit exclusion routing to create_tailored_resume. The prerequisite 'from the latest operationId' clarifies the calling sequence, and it notes earlier revisions remain for undo.

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