Skip to main content
Glama

Draft outreach messages

draftOutreach

Drafts a LinkedIn connection note and a short email from the candidate to a hiring manager, written in the candidate's voice from the resume draft, or from their CV or profile when there is no draft. Pass the jobId of a Clera role from searchCleraRoles / listMatches to aim them at one role; without it they are general. External board listings from searchJobs have no Clera jobId.

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

Input Schema

NameRequiredDescriptionDefault
jobIdNo

Output Schema

NameRequiredDescriptionDefault
draftsYes
linkedinNoteLengthYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare non-read-only, non-idempotent, non-destructive, closed-world, so the safety profile is already covered; the description adds real context beyond that, namely that output is written in the candidate's voice and mirrors their resume draft or CV/profile, and it discloses that Clera privately records inputs and results for usage tracking and support. It does not say whether drafts persist or are returned only, which keeps it from 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?

Opens with what is produced and in whose voice, then moves to the parameter's scoping rule, then the privacy note — a sensible priority order with no filler. The second sentence is dense with two tool references and a caveat, slightly loading more than one idea into a single sentence.

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 only one optional parameter and an output schema present, the definition covers everything an agent needs: what is generated, what it is based on, how to scope it to a role, the fallback when no draft exists, and a data-recording disclosure. Return values need no explanation because the output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 full burden and does: jobId is a Clera role identifier sourced from searchCleraRoles / listMatches, its absence means general (non-targeted) messages, and ids from searchJobs are explicitly unusable. That is more meaning than the bare uuid schema provides.

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 (drafts) and concrete artifacts (a LinkedIn connection note and a short email) from candidate to hiring manager, plus the source material (resume draft, else CV/profile). An agent knows exactly what it gets back and in whose voice, which no sibling name alone would convey.

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 the jobId: pass a Clera role id from searchCleraRoles / listMatches to target one role, omit it for general outreach, and warns that external board listings from searchJobs have no Clera jobId. It stops short of contrasting the tool with neighbors like requestOutreach or listOutreachRequests, but the context for calling it 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