Skip to main content
Glama

Read a shortlist

readShortlist
Read-onlyIdempotent

Open one shortlist Clera sent your company from its link (https://www.getclera.com/companies//review/): who was on it, and which of them are still waiting on your review, the same list the link opens in the dashboard.

Each candidate includes opportunityId, talentId, talentName, talentOneliner, fitHeadline and fitReason. noLongerInReview names the rest of the list, the ones no longer in your review queue: already acted on (see listPipeline or listPassed), dismissed, closed on the candidate's side, or on a paused role. notInReviewCount counts them all. When truncated is true the review queue was too large to load completely, so a still-waiting candidate may be missing here. opportunityId is a tool input only, pass it to requestIntro or passCandidate. Never show it to the user; refer to the candidate by name. For a full profile, call getCandidateProfile with the talentId.

Clera privately records this tool's inputs and results for usage tracking and support.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "link": "<link>"
    },
    "name": "readShortlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe shortlist link Clera sent, https://www.getclera.com/companies/<company>/review/<token>, or just the token at its end.
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.

Output Schema

NameRequiredDescriptionDefault
sentAtYes
roleNameYes
truncatedYes
candidatesYes
noLongerInReviewYes
notInReviewCountYes

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 readOnly/idempotent/non-destructive/closed-world, yet the description still adds real behavior: truncated=true means the review queue was too large and a waiting candidate may be missing, noLongerInReview enumerates the four reasons a candidate can drop off (acted on, dismissed, candidate-side close, paused role), and notInReviewCount counts them. It also discloses the privacy/logging behavior of inputs and results, which 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?

Purpose and the queue-vs-excluded distinction are front-loaded in the first two sentences, and the field inventory follows in a compact block. It is dense but nearly every clause earns its place; the closing privacy sentence is boilerplate but short and behaviorally relevant.

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 read-only, two-parameter tool with an output schema and full annotation coverage, the description is more than complete: it defines the returned fields' meaning, the truncation caveat that affects correctness of the answer, the handling rule for opportunityId, and the follow-up tool for a full profile. Nothing an agent needs to call it correctly or interpret its result 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?

Schema coverage is 100%, so both parameters are already documented, but the description adds genuine semantics for opportunityId: it is a tool input only, it must be passed to requestIntro or passCandidate, and it must never be shown to the user in favor of the candidate's name. That is operational meaning the schema does not carry, though orgId gets no treatment beyond 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?

"Open one shortlist Clera sent your company from its link" names a specific verb (open/read) and a specific resource (a shortlist identified by a link), and immediately scopes the result to "who was on it, and which of them are still waiting on your review." It distinguishes itself from listPipeline/listPassed by defining those as the places already-acted-on candidates live, so an agent can tell the siblings apart without opening their schemas.

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 clear routing for adjacent needs: "For a full profile, call getCandidateProfile with the talentId" and "pass it to requestIntro or passCandidate," plus pointers to listPipeline or listPassed for candidates already acted on. What it lacks is an explicit statement of when to prefer this tool over listPipeline for the review-queue question itself, so the choice on the primary use case is left mildly implicit.

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