Skip to main content
Glama

List my resumes

listResumes
Read-onlyIdempotent

The candidate's uploaded resumes, newest first, with which one is primary (the one Clera sends with introductions), plus the AI resume feedback if it has been generated: an overall and an ATS score, each out of 10, a summary, strengths and concrete improvements.

Add a new resume with importResumeFromLink (a Google Drive or iCloud share link) or getTalentDashboardLink upload_resume (a file on their computer). setPrimaryResume, deleteResume and refreshResumeFeedback act on what is here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resumesYes
feedbackYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, closed-world), so the bar is lower, yet the description still adds real behavior: result ordering, what 'primary' means operationally, the 0–10 score scale, and a note that inputs and results are privately recorded for support. It does not describe volume limits or what an empty state looks like, but for a zero-parameter read that is a minor gap.

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?

The core capability is front-loaded in the first sentence, and the second paragraph is an efficient routing block. The single sentence is dense — a long colon-appended clause listing feedback fields — and the data-collection note is arguably boilerplate, but nothing is redundant or buried.

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 complexity-free, parameterless read with an output schema available, the description is more than sufficient: it frames contents, ordering, the meaning of the primary marker, and how the result feeds the mutation tools. Nothing an agent needs to decide to call this instead of a sibling 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?

The tool takes no parameters, which is the baseline-4 case. The description adds nothing about inputs because there are none to explain, and the schema is trivially complete.

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 opens with a specific verb+resource ('The candidate's uploaded resumes') and immediately qualifies scope with ordering ('newest first'), the primary flag and its meaning ('the one Clera sends with introductions'), and the AI feedback payload. It is clearly separable from the add/mutate siblings named later, so an agent can distinguish it without opening a 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?

It explicitly routes creation to importResumeFromLink and getTalentDashboardLink upload_resume, and mutation to setPrimaryResume, deleteResume and refreshResumeFeedback, with the phrase 'act on what is here' implying list-then-act. It stops short of stating an explicit exclusion or precondition (e.g. what to do when the list is empty), so it is clear context rather than a full when/when-not contract.

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