Skip to main content
Glama

Review a tailored resume: revert changes, add job keywords

reviewTailoredResume
DestructiveIdempotent

Save the candidate's review of a tailored resume: every change id in revertedChangeIds goes back to their original wording, every other change keeps the rewrite. Send the complete set each time, so an empty list restores every rewrite. addKeywords puts job keywords into this copy's Skills as new skill changes: keywords listed as safe to add are already backed by the resume; a keyword the resume doesn't show goes in only after the candidate says they have it, never on your own judgment. addKeywordsToBase also adds them to their base resume. Clera rescores the match, renders a new PDF and marks it reviewed; applyToJob then sends that version. Take the change ids and keywords from getTailoredResume and confirm the set with the candidate first.

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

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": {
      "draftId": "<draftId>",
      "revertedChangeIds": "<revertedChangeIds>"
    },
    "name": "reviewTailoredResume"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYesThe draftId from getTailoredResume or listTailoredResumes.
addKeywordsNoJob keywords from getTailoredResume to add to Skills: safe-to-add ones, or missing ones the candidate confirmed having.
addKeywordsToBaseNoAlso add them to the candidate's base resume.
revertedChangeIdsYesEvery change id to put back to the original wording; all others keep the rewrite.

Output Schema

NameRequiredDescriptionDefault
tailoredYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description reinforces this with the complete-set semantics ("an empty list restores every rewrite") and discloses downstream side effects — rescoring the match, rendering a new PDF, marking it reviewed — plus the cross-object write via addKeywordsToBase. It does not cover failure modes or what happens when a change id is unknown, so it is useful but not exhaustive beyond the annotations.

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 and front-loaded: the core write semantics come first, then keyword policy, then downstream effects, then sourcing guidance. The trailing privacy-recording sentence is boilerplate that earns little space, and the definition is close to the upper limit of comfortable length.

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?

With an output schema present, return values need no explanation, and the description covers sourcing of both required parameters, the destructive-complete-set contract, the cross-resume side effect, and the resulting state changes — everything an agent needs to call this correctly.

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 100%, so baseline is 3, but the description adds real meaning: revertedChangeIds must be sent as a complete set with empty meaning "revert nothing," and addKeywords distinguishes safe-to-add keywords from unbacked ones requiring candidate confirmation, which the schema does not convey.

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 ("Save the candidate's review of a tailored resume") and immediately enumerates what the write does: revert listed change ids, keep the rest, optionally add keywords. This distinguishes it cleanly from getTailoredResume (read), listTailoredResumes, and applyToJob (which is named as the downstream consumer).

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: inputs come from getTailoredResume, the set must be confirmed with the candidate first, and applyToJob is named as the follow-on step. It also states a when-not rule for keyword additions ("never on your own judgment") and the condition under which a missing keyword may be added.

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