Skip to main content
Glama

List my pipeline

listMyPipeline
Read-onlyIdempotent

Every intro Clera has for the candidate, in every state, with the interview date where one is booked. Each row's tracker says where it sits on the candidate's job tracker (getTalentDashboardLink applications): columnTitle is the column, label the line on the card. Use them as given when the candidate asks where something is; tracker is null for rows not on it.

status: new (not reacted yet), questions (liked, company questions still open), interested (liked, Clera is working on it), not_submitted (liked, Clera reviewed it and did not present them), process (submitted to the company or interviewing), declined (candidate passed), withdrawn, no_match (Clera or the company said no), closed (the role closed). A not_submitted or no_match row carries reason: relay it as the why. undoMatchDecision reverses a declined row. Never show opportunityId or jobId.

Jobs the candidate applied to outside Clera are not here; listApplications returns those.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countsYes
opportunitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description goes beyond them by stating that tracker is null for rows not on the pipeline, that reason carries the 'why' on not_submitted/no_match rows, and that inputs and results are privately recorded for usage tracking and support. That privacy note is meaningful disclosure an agent would otherwise not have. It stops short of describing volume or ordering.

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 the purpose in one sentence, then moves through tracker fields, the status taxonomy, and edge cases in a logical order with no filler sentences. The status run is dense but each definition changes how an agent should interpret a row, so it earns its space; the long parenthetical clauses make it slower to parse than it needs to be.

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 read with annotations and an output schema, this covers everything an agent needs: what the rows are, how to interpret status, tracker, and reason, how to handle nulls, what must not be exposed, and where the excluded cases live. Nothing material is missing.

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 baseline is 4 and there is no input semantics to add. The description does invest in output-field meaning (columnTitle is the column, label is the line on the card, tracker null for unlisted rows), which is useful but overlaps an output schema that already exists.

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 resource and scope: 'Every intro Clera has for the candidate, in every state, with the interview date where one is booked.' It also draws an explicit boundary against the sibling that returns external applications ('Jobs the candidate applied to outside Clera are not here; listApplications returns those'), so an agent can separate the two without opening either 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 explicit when-not plus the alternative (external applications → listApplications) and an operational rule for how to use the tracker fields ('Use them as given when the candidate asks where something is'). It also names the reversal path for declined rows (undoMatchDecision) and the redaction rule (never show opportunityId or jobId), leaving little to inference.

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