Skip to main content
Glama

List passed candidates

listPassed
Read-onlyIdempotent

List candidates the company has passed on (declined) for its open roles. Use this when the company wants to see who was passed, or asks to undo a pass.

Each item includes opportunityId, talentId, talentName, roleName, and passedAt. passedAt is the opportunity's latest update time and may differ from when the pass happened. opportunityId is a tool input only, pass it to undoPass to undo a pass. Never show it to the user; refer to the candidate by name.

Returns one page at a time. When hasMore is true, pass nextCursor as cursor to get the next page.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (max 100).
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
cursorNoPass nextCursor from a previous call to get the next page.
roleIdNoOptional role ID to filter to a specific open role, resolved with the job tool's list command. Omit for all open roles.

Output Schema

NameRequiredDescriptionDefault
itemsYes
hasMoreYes
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 cover the read-only, idempotent, non-destructive profile, and the description still adds substantial behavior: passedAt is the opportunity's latest update time and may not equal the pass time, results are paginated with hasMore/nextCursor, and the inputs and results are logged by Clera. It also discloses a display constraint (never show opportunityId, refer to candidates by name) that the agent could not infer elsewhere.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scope sentence is front-loaded, followed by field semantics, then pagination, then the data-handling note, in descending order of decision value. Every sentence carries information an agent needs and there is no restatement of the tool name or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though an output schema exists, the description still lists the returned fields and flags the passedAt caveat, so the agent knows how to present results. Role filtering and org scoping are left entirely to the schema, which is acceptable but means the description is not fully self-contained for multi-org callers.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: opportunityId is 'a tool input only' that must be passed to undoPass and never surfaced to the user, and cursor should receive nextCursor when hasMore is true. Those usage constraints are not encoded in the schema.

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 states a specific verb and resource ('List candidates the company has passed on (declined) for its open roles') and adds scope ('for its open roles') that separates it from generic candidate search siblings such as searchCandidates. The gloss '(declined)' removes ambiguity about what 'passed' means.

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 gives explicit triggering language ('Use this when the company wants to see who was passed, or asks to undo a pass') and cross-references undoPass for the undo path. It does not state exclusions, e.g. that this covers only pass decisions and no other pipeline states, so it falls short of a full when/when-not treatment.

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