Skip to main content
Glama

Fill my resume draft

seedResumeDraft
Destructive

Fills the candidate's resume draft from data Clera already has: source "profile" is the merged career record (LinkedIn, uploaded resumes and GitHub combined), source "cv" is one parsed uploaded resume (the primary one, or resumeId from listResumes). Only empty sections are filled unless overwrite is true, which replaces what the candidate wrote; confirm before setting it. The result lists which sections were filled; read the draft afterwards and tidy it with editResumeDraft.

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": {
      "source": "<source>"
    },
    "name": "seedResumeDraft"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesprofile: the merged Clera record. cv: a parsed uploaded resume.
draftIdNoA resume version's draftId from readResumeDraft. Leave it out for the default version.
resumeIdNoWith source cv: a resumeId from listResumes; default is the primary resume.
overwriteNoReplace sections that already have content. Default false.

Output Schema

NameRequiredDescriptionDefault
filledYes
resumeYes

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 flag destructiveHint=true and non-idempotent, and the description adds real substance beyond them: only empty sections are filled by default, overwrite replaces candidate-authored content specifically, and confirmation is advised. It also discloses that inputs and results are recorded for usage tracking and support, and that the result enumerates which sections were filled.

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 action and source semantics before the overwrite caveat and the follow-up instruction. The trailing privacy disclosure is boilerplate but brief, so the text stays tight overall.

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?

An output schema exists, so return values need not be detailed, yet the description still tells the agent the result lists filled sections and to verify the draft afterward. With annotations covering the safety profile and the schema covering parameters, an agent has everything needed to call this 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?

Schema coverage is 100%, so the schema already documents all four parameters, making 3 the baseline. The description does add a bit beyond it, notably what 'profile' actually aggregates (LinkedIn, uploaded resumes, GitHub) and how resumeId pairs with source 'cv', but the overwrite and draftId semantics largely restate 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 a specific verb and resource ('Fills the candidate's resume draft') and immediately scopes the data origins for each source. It is clearly distinguishable from readResumeDraft and editResumeDraft, which are named and given distinct roles.

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?

Explains the two source modes, the resumeId cross-reference to listResumes, the default for draftId, and the follow-up workflow (read the draft, then tidy with editResumeDraft). It also warns to confirm before setting overwrite. It stops short of stating when not to use this tool versus other resume-population paths such as importResumeFromLink.

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