Skip to main content
Glama

TrueInterview

Update my résumé

update_resume

Replace sections of the candidate's saved résumé with what they told you: contact (merged field by field), headline, summary, skills, links, experience, education, projects. A section you send replaces that whole section, so call get_resume first and send the section complete; a section you leave out is untouched. Send every section you are changing in one call. Write only facts the candidate gave you or confirmed, show them the change before you save it, and never invent or embellish. When the candidate edits their own résumé file on their computer, sync the change without asking again: they made it, so it is their own words (the host still asks for its own approval); import_resume takes the whole file. The résumé as it was is filed in their library on the site before anything is replaced, and nothing is saved when that fails. With no résumé yet, this creates one. A new phone also becomes the saved phone forms get when that was the old résumé number. The answer links the saved résumé as a PDF in their saved style, ready to upload.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksNo
skillsNo
contactNo
summaryNo
headlineNo
projectsNo
educationNo
experienceNo
include_resume_fileNoRender the saved résumé as a PDF and return a link to it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well past the annotations: it discloses whole-section replacement semantics, that omitted sections are untouched, that the prior résumé is archived before replacement, that nothing is saved if archiving fails, that creation occurs when no résumé exists, and that a new phone propagates to the saved phone. Only slightly short of 5 because the interaction with destructiveHint=false is left implicit — the archive step explains it but isn't framed as such.

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 section list and replacement rule, but the later sentences pack sync policy, backup, creation, phone propagation, and output format into long run-on clauses. Every sentence earns its place, though readability suffers from density.

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 9-parameter nested mutation tool with no output schema, it covers replacement semantics, prerequisites, side effects, failure behavior, and the return value (PDF link in saved style). Nothing an agent needs to invoke 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?

With only 11% schema description coverage, the description carries the load: it enumerates the section parameters, clarifies that contact merges field by field while other sections replace wholesale, and implies include_resume_file via the PDF link in the answer. It does not explicitly name or explain include_resume_file as an opt-out, which keeps it from 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?

Opens with a specific verb and resource ("Replace sections of the candidate's saved résumé") and immediately names the sections it covers. It is distinguishable from get_resume (the read counterpart it tells you to call first) and import_resume (whole-file path).

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?

Explicit routing: call get_resume first and send each section complete; send all changed sections in one call; use import_resume when syncing an edited file instead. It even specifies that file sync needs no re-confirmation while normal edits require showing the candidate first.

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