Skip to main content
Glama

List resumes

list_resumes
Read-onlyIdempotent

Use this when the person asks to see their resumes, or a resume's id is needed. Returns master resumes and tailored versions, newest first, each with a label (company, job, date) and its ATS score. A limit above 50 is treated as 50. No contact details.

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

Input Schema

NameRequiredDescriptionDefault
roleNoOnly resumes whose role contains this, e.g. Director.
limitNo
sinceNoISO date-time; only resumes made after it.
cursorNonextCursor from the previous page.
searchNoCompany, job or name contains this.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / limit / maximum
      Removed value: -50
    • removedInput schema / properties / limit / minimum
      Removed value: -1
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive, so the description's added value is real: result ordering (newest first), what each row contains (label with company/job/date plus ATS score), the hard cap that a limit above 50 is treated as 50, and a privacy note that no contact details are returned. The silent clamping of limit is exactly the kind of behavior an agent would otherwise get wrong. The only gap is that it does not describe pagination termination alongside the cursor.

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 sentences, front-loaded with the invocation trigger before the content description. Every sentence adds information and none repeats the name or schema. Minimal, but well-ordered.

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?

Five optional parameters, no output schema, no nested objects. The description supplies the return shape, ordering, the limit caveat and an exclusion (no contact details), which covers what an agent needs to call it safely without an output schema.

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?

At 80% schema coverage the baseline is 3, and the description earns an increment by documenting the effective limit ceiling of 50, which is absent from the schema, and by fixing the default sort order, which bears on how since and cursor behave in practice.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('list' resumes) and immediately scopes the result: master resumes plus tailored versions, newest first, with label and ATS score. An agent can picture the payload. It stops short of naming a sibling such as get_resume to contrast single-item retrieval against this list.

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 two concrete triggers: when the person wants to see their resumes, and when a resume id is needed (i.e. as a precursor to a detail call). That is clear when-to-use guidance. It never states when not to use it or points at an alternative retrieval tool explicitly.

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