Skip to main content
Glama

List recommended candidates

listRecommendedCandidates
Read-onlyIdempotent

List the candidates Clera picked for your roles that are awaiting your review, the same set the Review tab of the dashboard shows minus the intro requests candidates sent themselves.

Each item includes opportunityId, talentId, talentName, talentOneliner, fitHeadline (AI-generated fit summary), and roleName. opportunityId is a tool input only, pass it to requestIntro or passCandidate. 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": "listRecommendedCandidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (max 20).
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 role, resolved with the job tool's list command. Omit for all roles.

Output Schema

NameRequiredDescriptionDefault
itemsYes
hasMoreYes
nextCursorYes
totalCountYes

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 declare read-only, idempotent, non-destructive, closed-world, so the safety profile is covered; the description goes further by disclosing pagination semantics ("Returns one page at a time"), the hasMore→cursor loop, and a privacy notice that inputs and results are recorded for usage tracking. It also warns never to display opportunityId, which is a behavioral constraint nothing in the structured fields 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?

Front-loads purpose, then returns, then usage warnings, then pagination — a sensible order with no filler sentences. The enumerated return fields partially duplicate the existing output schema, making that paragraph the weakest use of space.

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 paginated list tool with an output schema, everything an agent needs is present: scope, sibling handoffs, pagination loop, ID handling rules, and a data-handling disclosure. The only near-redundancy is restating return fields already in the output schema, which costs nothing in correctness.

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 it: cursor is tied to the hasMore flag and nextCursor, and opportunityId's dual role as both returned field and downstream input is explained. Limit and orgId semantics are left entirely to the schema, which keeps this just short of a 5.

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?

States a specific verb and resource ("List the candidates Clera picked for your roles that are awaiting your review") and pins the scope precisely by cross-referencing the dashboard's Review tab and excluding self-sent intro requests. That exclusion distinguishes it from the pending-intro and intro-request siblings without the agent needing to open another 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?

Gives concrete downstream routing: opportunityId "is a tool input only, pass it to requestIntro or passCandidate," naming both alternatives and the action that consumes the ID. It does not, however, say when to reach for this list versus broader discovery tools like searchCandidates or similarCandidates, so the when-not guidance is partial.

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