Skip to main content
Glama

List pending intro requests

listPendingIntroRequests
Read-onlyIdempotent

List candidates who have expressed interest in the company's roles and are waiting for a company decision, the intro requests shown in the Review tab of the dashboard.

Each item includes opportunityId, talentId, talentName, talentOneliner (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": "listPendingIntroRequests"
  }
}

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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: pagination via hasMore/nextCursor, the rule that opportunityId must never be surfaced to the user, and a note that inputs/results are logged for usage tracking.

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 the purpose in the first sentence, then return shape, then pagination, then privacy. Structure is strong, but the returned-field enumeration partially duplicates the output schema and the privacy/logging sentence reads as boilerplate.

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?

With an output schema present, full annotation coverage, and 100% schema description coverage, the description only needed to supply the review-queue framing, the display rule for opportunityId, and pagination guidance, all of which it does.

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 coverage is 100%, so limit, orgId, cursor, and roleId are already documented, and the description's pagination sentence largely restates the cursor field. The opportunityId discussion concerns a returned field rather than an input, so it adds output meaning, not parameter meaning; baseline 3 applies.

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 (list), specific resource (pending intro requests), and scopes it precisely as 'candidates who have expressed interest and are waiting for a company decision,' even mapping it to the Review tab of the dashboard. That framing cleanly separates it from sibling lists like listInterviewRequests, listOutreachRequests, and listPassed.

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?

The 'waiting for a company decision' framing gives a clear condition for when this list is the right one, and it names the follow-on actions (requestIntro, passCandidate) that consume the results. It stops short of explicit exclusions such as when to prefer listInterviewRequests or listOutreachRequests instead.

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