Skip to main content
Glama

List searches

listRoleSearches
Read-onlyIdempotent

List your company's Searches: each one looks for people for a role (or explores without one) across the Clera pool, your team's network and, when turned on, outside Clera.

Returns each Search's role, status, schedule, next run, how many people it found and whether you can change it. Pass jobId (from readJob) to see only one role's Searches. 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": "listRoleSearches"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdNoOnly Searches for this role.
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
cursorNo

Output Schema

NameRequiredDescriptionDefault
hasMoreYes
searchesYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description goes beyond them by naming the returned fields (role, status, schedule, next run, match count, editability), describing the pagination loop, and disclosing that inputs and results are privately recorded for usage tracking and support.

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 and scope, then filtering, then pagination, then a separate required disclosure line. Each sentence carries information; only the privacy notice adds bulk, and that is likely mandated rather than padding.

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 filtered read-only list tool with an output schema present, the description covers purpose, filtering, pagination looping, and multi-org ambiguity indirectly via the schema. The only real gap is that orgId's multi-organization semantics are left entirely to the schema, which is acceptable given the output schema and annotations.

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 67%, so the schema already documents jobId and orgId. The description adds real value for jobId by naming its upstream source (readJob) and for cursor by tying it to nextCursor/hasMore. It says nothing about orgId behavior beyond what the schema states, so the net addition is moderate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List your company's Searches') and explains what a Search actually is (finds people for a role, or explores without one, across the Clera pool, team network, and outside Clera). That conceptual grounding is stronger than a bare listing. It doesn't directly contrast with getRoleSearch or readJob except as a source for jobId, so it stops short of full sibling differentiation.

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?

Gives concrete when-to-do-what guidance: pass jobId (from readJob) to narrow to one role's Searches, and call again with cursor set to nextCursor when hasMore is true. That is actionable routing without an explicit statement of when not to use this tool or which sibling replaces it.

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