Skip to main content
Glama

Rewrite a resume

request_resume_update
Destructive

Rewrite a resume from a natural-language instruction using the tuned LLM resume pipeline (ATS-aware, keeps the resume's own language). Runs asynchronously — returns a task_id immediately; the rewrite typically takes a few minutes, and a completion (or failure) message is posted into the user's chat when it finishes; get_task_status(task_id) reports progress and the outcome. It is for substantive rewrites ('rewrite my summary for a senior role', 'tighten all bullets', 'shorten the resume'); small structural edits are update_resume_section. NOT supported: translating the whole resume (that is translate_resume) and adding a photo (only the resume editor uploads one) — such requests fail. Consumes one resume update from the user's plan. source_text carries the user's own resume or full account of their experience, verbatim: the resume is then rebuilt from that text instead of being edited from the instruction. Returns 'not_found' if the resume does not belong to the current user, 'limit_exceeded' naming the day it frees up if the plan quota is reached, and 'invalid_payload' if source_text is longer than 20000 characters.

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": {
      "input": "<input>"
    },
    "name": "request_resume_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
statusNoAlways 'processing' — the rewrite runs asynchronously.processing
task_idYesBackground task id (informational; the rewrite runs asynchronously).
resume_idYesId of the resume being rewritten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes far beyond the annotations (which only declare destructive/non-idempotent/non-readonly): it discloses asynchronous execution with an immediate task_id, a multi-minute duration, a chat completion message, progress via get_task_status, plan-quota consumption, and specific failure modes with their identifiers. The destructiveHint=true is corroborated rather than merely repeated.

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?

Dense but purposefully so: capability first, then async contract, then routing, then cost, then errors. Every sentence carries information, though the long mid-paragraph clause about source_text placement costs some scannability for a definition this packed.

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 an async, quota-consuming, destructive mutation, the description covers initiation, polling, duration, notification, cost, and named error outcomes; the output schema handles return shape. Nothing an agent needs to invoke this correctly and set user expectations 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?

Adds real meaning for source_text — that it is the user's own verbatim text and that the resume is rebuilt from it rather than edited from the instruction, plus the 20000-char failure condition. It says comparatively little extra about instruction or resume_id beyond the schema's own examples, leaving a small gap given the reported coverage signal.

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 and resource ('Rewrite a resume from a natural-language instruction using the tuned LLM resume pipeline') and immediately scopes it against two siblings: substantive rewrites here versus 'small structural edits are update_resume_section'. An agent can pick the right tool without opening any schema.

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?

Gives concrete when-to-use examples ('rewrite my summary for a senior role', 'tighten all bullets', 'shorten the resume'), names the alternative for small edits, and lists explicit exclusions routed elsewhere (whole-resume translation → translate_resume, photo upload → editor only). Both positive and negative routing are covered.

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.