Skip to main content
Glama

Read my resume draft

readResumeDraft
Read-onlyIdempotent

The candidate's resume-builder draft: profile, experience with bullets, education, skills, languages, links and the design settings. This is the structured resume the candidate edits on the dashboard and turns into a PDF; it is separate from the uploaded resumes in listResumes. Empty until seedResumeDraft or editResumeDraft creates it.

A candidate can keep several versions (say, one per kind of role). drafts lists every version with its draftId; pass draftId here and to editResumeDraft, seedResumeDraft or generateResumePdf to work on one that isn't the default. manageResumeVersions creates, renames, deletes or switches the default.

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

Input Schema

NameRequiredDescriptionDefault
draftIdNoA resume version's draftId from readResumeDraft. Leave it out for the default version.

Output Schema

NameRequiredDescriptionDefault
draftsYes
resumeYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavior: the draft is empty until seedResumeDraft or editResumeDraft creates it (state dependency), multiple versions can coexist, and inputs/results are logged for support. It does not cover error cases or what happens when a stale draftId is supplied, keeping it short of a 5.

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?

Three short paragraphs, front-loaded with what the resource is, then versioning, then the disclosure notice. Nearly every sentence carries routing or state information; the privacy sentence is boilerplate but brief and standard.

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 a rich annotation set, an output schema and a fully documented single parameter, the remaining burden on the description is state and sibling routing — both covered. Nothing an agent needs in order to call this correctly is missing.

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% and the single optional draftId is documented, so the baseline is 3. The description adds meaning the schema lacks: omitting the id targets the default version, and the same id is the shared handle across editing, seeding and PDF generation, which clarifies the versioning model rather than restating the 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 resource (the resume-builder draft) and enumerates its contents — profile, experience with bullets, education, skills, languages, links, design settings — then explicitly separates it from the uploaded resumes returned by listResumes. An agent can distinguish this from getTailoredResume or listResumes 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 Guidelines5/5

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

It states exactly when the draftId argument matters (non-default versions), where to get the ids (drafts lists every version with its draftId), and which sibling tools accept the same id (editResumeDraft, seedResumeDraft, generateResumePdf). It also points to manageResumeVersions for create/rename/delete/default-switch, giving the agent a clear routing map.

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