Skip to main content
Glama

List my tailored resumes

listTailoredResumes
Read-onlyIdempotent

The resumes Clera tailored to the candidate's tracked applications (generateApplicationDocuments with kinds resume), newest edit first: each with its draftId, the applicationId it belongs to (listApplications), the match score for that role before and after tailoring (0-100 with a band), how many rewrites it kept and when the candidate last reviewed it. applyToJob sends the tailored resume for that application's job. getTailoredResume shows every change and the PDF.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoPass nextCursor from a previous call to get the next page.

Output Schema

NameRequiredDescriptionDefault
hasMoreYes
nextCursorYes
tailoredResumesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the safety profile is covered. The description adds useful behavior: default ordering by most-recent edit and the privacy notice that inputs/results are recorded. It says nothing about page size or how the cursor terminates, which leaves paging semantics to the schema.

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 purpose, then sibling routing, then a short disclosure sentence. The middle clause enumerating return fields (draftId, applicationId, scores, rewrite counts) is dense and partly redundant with the output schema, which is the only real waste.

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

Completeness3/5

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

An output schema exists, so the field-by-field enumeration is largely redundant, and the read-only/idempotent contract is handled by annotations. What remains thin is pagination behavior for the sole cursor parameter; otherwise an agent has enough to call it correctly.

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?

Only parameter is cursor and the schema documents it at 100% coverage, so the baseline is 3. The description's 'newest edit first' implies the ordering the cursor pages over but never explains pagination behavior or cursor expiry, so it adds little beyond the schema.

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 the specific resource (resumes Clera tailored) narrowed to the candidate's tracked applications, with ordering ('newest edit first'), and implicitly contrasts with getTailoredResume as the detail view. An agent can distinguish it from listResumes and getTailoredResume without opening any 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?

Routes the agent well: getTailoredResume for the full diff/PDF, applyToJob for sending, listApplications for the owning application id, generateApplicationDocuments for how these get created. It gives no explicit exclusion ('do not use this to...'), so it stops short of a 5, but the context is 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