Skip to main content
Glama

Edit my resume draft

editResumeDraft
DestructiveIdempotent

Replaces one section of the candidate's resume draft with the value sent, and creates the draft if none exists. Sections: profile, work (roles with plain-text bullets, newest first, dates as YYYY-MM, empty endDate means present), education, skills ({name, group}), languages ({name, level}), links ({type, label, url}; url is a full web link like github.com/you, so drop or fix any link that is only a label, handle or email), design (templateId harvard_classic | ats_clean | executive_serif, accentColor hex, fontSizePt (8–13 in 0.5 steps, 10.5 is standard), sectionOrder, templateOptions). Read the draft first and send the whole section back with your changes; a section is replaced, never merged, so anything you leave out of the value is gone. This is how you rewrite bullets or a summary for the candidate: propose the text, get a yes, then send it here.

Clera privately records this tool's inputs and results for usage tracking and support.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resumeYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description goes well beyond them by explaining exactly what is destroyed ('anything you leave out of the value is gone') and that the section is replaced rather than merged. It also discloses the implicit create-if-absent behavior and the read-before-write prerequisite, which annotations do not convey.

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?

The core action and its destructive replacement semantics are front-loaded, and every sentence carries content. However, the section-by-section catalogue is delivered as one dense paragraph rather than a scannable list, which makes the long middle sentence harder to parse than it needs to be.

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 tool with seven mutually-exclusive section shapes, the description covers all of them plus the read-before-write loop and the replace-not-merge contract. An output schema exists, so return values need not be described, and the draftId parameter is already documented in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even at 100% schema coverage, the description adds semantics the schema cannot express: dates as YYYY-MM with empty endDate meaning present, work bullets are plain text and ordered newest first, empty endDate semantics, skills as {name, group}, and the rule that link url must be a real URL and label-only links must be dropped or fixed. The design guidance (templateId options, hex accentColor, fontSizePt in 0.5 steps with 10.5 as the standard) tells the agent how to pick values rather than just their type.

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 ('Replaces one section of the candidate's resume draft') plus a side effect ('creates the draft if none exists'), then enumerates the section vocabulary. It also names the sibling it depends on (readResumeDraft), so the agent can place it against read/seed/delete resume tools without opening a 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 explicit ordering ('Read the draft first'), an explicit alternative workflow ('propose the text, get a yes, then send it here'), and an explicit failure mode to avoid ('a section is replaced, never merged'). The only thing missing is a named when-not-to-use case, but the workflow instruction is unambiguous.

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