Skip to main content
Glama

Resumeily

Update resume

update_resume

Edits a temporary resume draft identified by its draft_token; resumes already saved in a Resumeily account are never affected. Changes are reversible: the previous 10 versions are kept and undo: true restores the most recent one. Each section included in resume is set to the content provided (a complete section, such as the full experience list); omitted sections are unchanged. Appearance fields (template, colors, font, title) change only when provided.

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

Input Schema

NameRequiredDescriptionDefault
fontNoOne of: Arial, Helvetica, Times New Roman, Georgia, Verdana, Courier New, Roboto, Open Sans, Lato, Montserrat, Poppins, Rubik, Inter, Playfair Display, Merriweather.
undoNoWhen true, reverts the most recent change by restoring the previous version; other fields are ignored.
titleNoResume title, e.g. 'Jane Doe – Frontend Developer'.
colorsNo
resumeNoSections to update. Each included section is set to the content provided; omitted sections are unchanged.
templateNoTemplate id, such as 'classic', 'modern' or 'slate'. Defaults to 'classic'.
draft_tokenYesPrivate token that identifies the resume draft (returned when the draft is created).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses the facts that matter most for a mutation: changes are reversible, the previous 10 versions are retained, and `undo: true` restores the most recent one. It also explains that included sections are replaced wholesale (a complete section must be supplied, not a patch) while omitted sections and unprovided appearance fields are left untouched — a merge semantic no annotation conveys. This is consistent with destructiveHint=false and with idempotentHint=false, since each call creates a new version.

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?

Four sentences, each carrying a distinct constraint, with the most consequential scope limit (saved resumes untouched) front-loaded before the reversibility and merge semantics. No filler and no repetition of the title.

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 7-parameter tool with nested objects and only 86% schema coverage, the description covers mutation semantics, reversibility and partial-update behavior well. With no output schema, though, it says nothing about what the call returns (updated draft, version id, preview link), which an agent needs to chain into preview_resume.

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 already 86%, so the baseline would be 3, but the description adds genuine meaning: `resume` is replace-per-section rather than a deep merge, omission means "leave unchanged," and template/colors/font/title are only applied when present. It does not restate the token's origin or the undo precedence rule that the schema itself documents, so it complements rather than duplicates.

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?

"Edits a temporary resume draft identified by its draft_token" gives a specific verb plus resource, and the clause "resumes already saved in a Resumeily account are never affected" pins the exact scope. That scope statement implicitly separates it from create_resume and from anything operating on saved resumes, so an agent can route without opening the 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?

The description clearly establishes the operating context (temporary draft, never saved resumes) and states the undo path, which is real when-to-use guidance. It stops short of naming siblings — it never says to use create_resume for new drafts or preview_resume to inspect the result — so the routing is inferred rather than explicit.

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