Skip to main content
Glama

Read a tailored resume

getTailoredResume
Read-onlyIdempotent

One resume Clera tailored to a tracked application, by that application's applicationId (listApplications) or its draftId (listTailoredResumes): every rewrite with its change id, section (title, summary or bullet), the original and the new wording, the reason, and whether the candidate reverted it; the match score for the role before and after (0-100, band, matched and missing requirements); and a PDF link that expires after an hour. tailored is null when that application has none yet, or while generateApplicationDocuments is still writing it. Rewrites only rephrase facts already on the candidate's resume; reviewTailoredResume reverts the ones they don't want.

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getTailoredResume"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdNoInstead of applicationId: the draftId from listTailoredResumes.
applicationIdNoThe id of a listApplications entry.

Output Schema

NameRequiredDescriptionDefault
tailoredYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: the PDF link expires after one hour, the null result both when no tailored resume exists and during generation, and the guarantee that rewrites only rephrase facts already on the resume. It also discloses input/result recording for usage tracking, which an agent should know before surfacing results.

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?

Front-loaded with the core identification and result shape, but the payload is crammed into one very long sentence enumerating return fields, and the closing privacy sentence is boilerplate. It earns most of its space but could be split for scanability.

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 read tool with two optional UUIDs, the description covers identification, return shape, null states, and the downstream revert workflow. Return values are described even though an output schema exists, leaving no ambiguity about what an agent will get back.

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?

Schema coverage is 100% and the schema already documents each parameter's source ('the draftId from listTailoredResumes', 'The id of a listApplications entry'). The description restates the same mapping without adding format, precedence, or error behavior beyond what the schema provides, so baseline 3 applies.

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 ('One resume Clera tailored to a tracked application') plus the two lookup keys, and names the sibling tools that produce those keys (listApplications, listTailoredResumes). An agent can distinguish this from listTailoredResumes or reviewTailoredResume 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing for how to obtain each id, points at reviewTailoredResume for reverting rewrites, and warns that tailored is null while generateApplicationDocuments is still writing. It lacks an explicit 'do not use this when…' exclusion, but the alternative paths are clear.

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