Skip to main content
Glama

List prospects

listProspects
Read-onlyIdempotent

List your company's prospects: everyone your team viewed, shortlisted, revealed or contacted from People Search, most recently touched first, with status, tags, the roles they are shortlisted for and any contact details your team revealed.

Filter by status, tag, role (jobId from readJob) or a name/company/title query. When hasMore is true, call again with cursor set to nextCursor.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
jobIdNoOnly people shortlisted for this role.
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
queryNoMatches name, company or title.
cursorNo
statusNo

Output Schema

NameRequiredDescriptionDefault
hasMoreYes
prospectsYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the description isn't carrying the safety burden. It still adds real context beyond them: default ordering, what each record contains (status, tags, shortlisted roles, revealed contact details), and the cursor/hasMore pagination contract. The closing note about privately recording inputs and results for usage tracking and support is an unusual but genuinely useful disclosure.

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?

Three tight paragraphs: scope first, filtering and pagination second, disclosure last. Nothing is redundant, though the final data-recording sentence sits a bit awkwardly after the operational instructions and could be folded in more smoothly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, zero-required list tool with an output schema, the description covers scope, filters, ordering and the pagination loop, which is what an agent needs to invoke it correctly. Return-value details are partly restated even though the output schema exists, and no guidance is given on sensible default page sizes or what an empty result means.

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 only 50%, but the description compensates for most of the gap by explaining that status/tag are filters, that jobId should come from readJob, that query matches name/company/title, and that cursor pairs with nextCursor. Only orgId is left entirely to the schema, which does document it.

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?

The description names a specific verb and resource ('List your company's prospects') and then defines the population precisely: 'everyone your team viewed, shortlisted, revealed or contacted from People Search.' It also states ordering ('most recently touched first') and returned fields, so an agent can distinguish this from sibling list tools like listMyPipeline 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent exactly how to narrow results ('Filter by status, tag, role (jobId from readJob) or a name/company/title query') and gives an explicit pagination loop ('When hasMore is true, call again with cursor set to nextCursor'). What's missing is any exclusion or contrast with sibling tools, e.g. when to prefer this over listMyPipeline or listSourcingFeed.

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