Skip to main content
Glama

List my matches

listMatches
Read-onlyIdempotent

The top of the candidate's Matches page, in the order the page shows them: companies that asked to talk to them, their active roles, then the first 50 roles of their ranked list. A ranked role Clera hasn't written up for them yet is kind open_role, with no whyMatch. total is how many roles the whole page holds and pendingCount how many still wait on the candidate; the page itself scrolls past the rows returned here.

Rows with introRequested true are companies that asked to talk to this candidate; they come first. A row with applyOwnership referral_link (via partnerLabel, e.g. micro1) gets no intro: liking it hands the candidate referralUrl to apply on the partner's own site, and those roles sit at the bottom of the list. status questions means the candidate liked the role and the company still needs answers to its questions — answerRoleQuestion handles those. Roles already passed on, closed or marked no match are not here; listMyPipeline has everything.

Act on a row with likeMatch or declineMatch (jobId, position and companyName from the row). For the full role, readMatch takes the row's opportunityId; an open_role row has none, so readJobListing takes its jobId. Never show opportunityId or 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": "listMatches"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
totalYes
matchesYes
pendingCountYes
introRequestCountYes
openQuestionCountYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses row semantics (introRequested, kind=open_role with no whyMatch, applyOwnership referral_link rows that get no intro and sort last), the meaning of total and pendingCount, and that the page scrolls past returned rows. It even discloses that inputs and results are recorded for usage tracking and support, which is behavior no annotation conveys.

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?

Content is front-loaded with ordering and every paragraph carries operational information, but the prose is dense and contains rough spots (e.g. 'is kind open_role', the run-on referral_link sentence) that slow parsing. The privacy sentence is boilerplate yet presumably mandated.

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 zero-parameter list tool with an output schema and full read-only annotations, the description covers everything an agent needs: what comes back, in what order, what each special row type means, what is omitted, and which sibling to call next.

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 zero parameters, so the schema baseline is 4. The description still adds value by explaining which row fields (jobId, position, companyName, opportunityId) feed the sibling action tools, though that is output-side rather than input-side semantics.

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 names a specific resource (the candidate's Matches page) and states its exact scope and ordering: intro-requested companies first, then active roles, then the first 50 ranked roles. It explicitly distinguishes itself from listMyPipeline ('listMyPipeline has everything') and from listPassed, so an agent can route 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit next-step routing: likeMatch/declineMatch to act on a row, readMatch for the full role via opportunityId, readJobListing for open_role rows that lack one, and answerRoleQuestion for status=questions. It also states what is excluded (passed, closed, no-match) and points to the alternative that covers those.

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