Skip to main content
Glama

List my cover letters

listCoverLetters
Read-onlyIdempotent

The candidate's saved cover letters, newest edit first, 20 at a time: letterId, name, the job description each was written for, the full text and a PDF link valid for an hour. generateCoverLetter writes a new one; editCoverLetter changes one.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
hasMoreYes
lettersYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds real context beyond that: page size of 20, sort order by newest edit, the exact fields returned, a PDF link that expires after an hour, and a disclosure that inputs and results are logged. The ephemeral link and pagination details are behavior an agent cannot infer from structured fields.

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 what is returned, then ordering, then the sibling routing, all in two dense sentences with no filler. The trailing sentence about private recording is boilerplate disclosure but is short and separated, so it does not obscure the core content.

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 simple read-only list tool with one optional parameter, the description covers ordering, page size, returned fields, link lifetime, and sibling routing. An output schema exists, so return-value detail is already handled, and nothing an agent needs 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?

There is a single optional cursor parameter already documented at 100% schema coverage, so the baseline is 3. The description earns an extra point by stating the page size of 20 and the ordering, which tells the agent why and how to paginate beyond what the cursor description alone conveys.

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?

Names a specific verb and resource (list the candidate's saved cover letters) and adds scope: newest edit first, 20 at a time. It also explicitly separates itself from generateCoverLetter (writes a new one) and editCoverLetter (changes one), so an agent can distinguish it from siblings without opening schemas.

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 correctly by naming the two write alternatives and what each does, implying this tool is for reading existing letters. It lacks an explicit 'do not use this to create/edit' exclusion or a note on when to page with cursor versus stopping, so it falls just short of full when/when-not guidance.

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