Skip to main content
Glama

List the hiring pipeline

listPipeline
Read-onlyIdempotent

List the company's hiring pipeline, the same board the Pipeline page of the dashboard renders: every candidate grouped by stage, with a count per stage.

Stages in order: review (awaiting the company's review), intro_requested (intro in progress), introduced (awaiting first interview), interviewing, offer, hired. Each candidate includes opportunityId, talentId, talentName, roleId, roleName, and for interviewing candidates interviewStage (e.g. "Technical screen (2 of 3)") and nextInterviewAt. When nextInterviewIsDayOnly is true only the day is agreed: nextInterviewAt is that day at 00:00 UTC, so name the day and never a time.

roleCounts gives the board total per role, largest first. It is the only candidate count per role; the job tool's list command carries none.

Use it for any question about how many candidates are in the pipeline, how many a role has, who is interviewing, or which stage someone is at. To decline someone already in the pipeline, pass their opportunityId, talentName and roleName to passCandidate; a review row with a null opportunityId is declined from listRecommendedCandidates instead. Counts cover the whole stage, candidates are capped by candidatesPerStage.

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

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
roleIdNoOptional role ID to filter to a specific role, resolved with the job tool's list command. Omit for all roles.
candidatesPerStageNoHow many candidates to list per stage (max 50). Counts always cover the whole stage.

Output Schema

NameRequiredDescriptionDefault
stagesYes
roleCountsYes
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 cover the safety profile (readOnly, idempotent, non-destructive, non-open-world), yet the description still adds substantial context beyond them: the exact stage ordering and what each stage means, the truncation rule (counts cover the whole stage, rows are capped by candidatesPerStage), the null-opportunityId edge case, and a data-recording disclosure. The nextInterviewIsDayOnly rule (day-only means 00:00 UTC, never name a time) is exactly the kind of trap-avoidance an agent cannot get from annotations.

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-loaded with purpose, then stage vocabulary, then result fields, then usage routing — a sensible order for an agent scanning top-down. It is on the long side and one sentence ("Counts cover the whole stage, candidates are capped by candidatesPerStage") largely duplicates the candidatesPerStage schema text, but nothing is pure noise.

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?

Covers every open question for a filtered read tool: what the board contains, stage ordering, per-candidate fields, the ambiguous day-only timestamp, and where role-level totals live (roleCounts, with the note that the job tool's list command carries none). An output schema exists, so the field walkthrough is a bonus rather than a necessity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so orgId, roleId (including the UUID format and the "resolved with the job tool's list command" hint) and candidatesPerStage are already fully documented. The description restates the capping behaviour and count semantics but adds no syntax or format detail the schema lacks, so it earns the baseline rather than more.

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+resource ("List the company's hiring pipeline") and immediately scopes it with a concrete metaphor ("the same board the Pipeline page of the dashboard renders") plus the shape of the result (candidates grouped by stage, counts per stage). The "company's" qualifier implicitly separates it from the personal-scope sibling listMyPipeline, so an agent can pick between them 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?

Gives an explicit when-to-use list ("any question about how many candidates are in the pipeline, how many a role has, who is interviewing, or which stage someone is at") and routes onward for the adjacent action: pass opportunityId/talentName/roleName to passCandidate, and use listRecommendedCandidates instead when a review row has a null opportunityId. Both the alternative and the condition selecting it are named.

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