Skip to main content
Glama

Copy a resume

create_resume_version

Create a new draft resume as a copy of an existing one — the original is left untouched. Optionally pass a vacancy_id to tailor against; it names the draft and links the copy to that vacancy (shown on the vacancy card and as a badge in the resume manager). Counts as one resume generation against the user's plan. Returns 'not_found' if the source resume (or vacancy) does not exist or does not belong to the current user, and 'limit_exceeded' naming the day it frees up if the plan quota is reached.

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": "create_resume_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
idYesId of the newly created draft resume.
nameYes
vacancy_idNo
content_versionNoContent version of the new copy: a hash of the content, so it equals the source's until either changes. update_resume_section takes it as expected_content_version. The copy's entry ids differ from the source's.
source_resume_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the source remains untouched, that the call consumes one resume generation against the plan quota, that the copy stays linked to the vacancy, and it names two concrete failure modes ('not_found' for foreign/missing resources, 'limit_exceeded' with the freeing date). That is meaningful side-effect and cost disclosure the annotations do not carry.

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, front-loaded with the core action and the non-destructive guarantee, followed by optionality, cost, and error semantics in descending priority. No filler or repetition.

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 non-idempotent creation tool with quota implications, it covers the safety profile, the cost model, and the error contract; an output schema exists so return-shape detail is correctly omitted. Nothing an agent needs in order to call it correctly is missing.

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?

The description explains vacancy_id's downstream effects (naming the draft, linkage, badge in the resume manager) beyond a bare identifier, but it never mentions the 'name' parameter or the source_resume_id requirement. With schema coverage reported at 0% and a nested input object, the description only partially compensates for the parameter documentation gap.

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 verb and resource ('Create a new draft resume as a copy of an existing one') and immediately disambiguates from siblings like rename_resume, delete_resume and get_resume by stating the original is untouched. An agent can select this over the many other resume tools 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?

It gives a clear context for use (copying an existing resume into a draft) and explains the optional tailoring path via vacancy_id, including where the link surfaces. It does not explicitly name alternatives such as get_resume or rename_resume for non-copy needs, so routing guidance stops just short of full when/when-not coverage.

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.