Skip to main content
Glama

Tailor a resume step by step

tailor_resume

Use this only in the step-by-step path, when create_tailored_resume is unavailable or failed, to tailor a resume from the operationIds of import_resume and analyze_job_offer. For a new request to tailor a resume to a job post, use create_tailored_resume instead. Runs the same adapter as the Matchaa website (rewords the experience with the job post's vocabulary, never invents skills) and keeps a private draft PDF with a before/after report and source evidence. Prefer the operationIds returned by import_resume and analyze_job_offer; otherwise pass the attached PDF (cvFile) or the resume text, with the job post text. Pass the job post's language unless the user asked for another. If interrupted, call it again with exactly the same arguments to resume. Do not use for wording or design changes to a tailored resume; use update_resume or rewrite_resume_section.

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": {
      "guestToken": "<guestToken>"
    },
    "name": "tailor_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvFileNo
cvTextNo
languageNofr
offerTextNo
guestTokenYes
templateIdNoclassique
offerOperationIdNo
sourceOperationIdNo

Output Schema

NameRequiredDescriptionDefault
errorNo
resultNo
statusYes
recoveryNo
downloadUrlNo
operationIdYes
expiresInSecondsNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses substantive behavior: it runs the same adapter as the website, rewords experience with the job post's vocabulary, never invents skills, and leaves a private draft PDF with a before/after report and source evidence. The idempotent retry semantics are also behavior an agent could not infer from annotations alone.

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?

Every sentence carries information — gating condition, alternative, behavior, parameter preference, language, retry, exclusion — with the precondition front-loaded. The first sentence is densely nested ('operationIds of import_resume and analyze_job_offer') and needs a second read, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutating tool with an output schema, the definition covers the decision logic, input sourcing, behavior, and return artifact described in prose. The only shortfall is the unmentioned required guestToken and the undocumented template selector, which an agent must resolve purely from the schema.

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 description coverage is 0%, so the description carries the burden, and it does well on the core fields: it prefers sourceOperationId/offerOperationId from the sibling tools, falls back to cvFile or resume text plus the job post text, and states the language convention. It never explains the required guestToken or the templateId selector (19 enum values), which is a real gap for 8 parameters and one required field.

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 names a specific verb and resource ('tailor a resume') and immediately scopes the input source ('from the operationIds of import_resume and analyze_job_offer'). It explicitly distinguishes itself from the sibling create_tailored_resume, so an agent can pick between them without opening either 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?

It states a hard precondition ('only in the step-by-step path, when create_tailored_resume is unavailable or failed'), names the default alternative for new requests, and gives a negative rule ('Do not use for wording or design changes; use update_resume or rewrite_resume_section'). It also covers the interrupted-run case with a concrete recovery instruction (retry with identical arguments).

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