Skip to main content
Glama

List a role's Sourcing feed

listSourcingFeed
Read-onlyIdempotent

List the people waiting on a role's Sourcing feed (jobId from readJob): people Clera's sourcing run approved for the role and has not contacted yet, newest first, each with a 0-100 fit and the judge's one-line reason. roleSearchId is null when the role has no Sourcing feed. To pass or reach out, use setRoleSearchDecision with roleSearchId and the person's roleSearchPersonId; a yes there starts outreach. 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

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": {
      "jobId": "<jobId>"
    },
    "name": "listSourcingFeed"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
cursorNo

Output Schema

NameRequiredDescriptionDefault
peopleYes
hasMoreYes
waitingYes
nextCursorYes
roleSearchIdYes

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, idempotentHint and destructiveHint=false, so safety is covered; the description adds ordering (newest first), the null-feed condition for roleSearchId, cursor-based pagination loop, and a data-recording notice for inputs/results. Return field detail is partly carried by the output schema, so a small amount of behavioral surface (e.g. what happens if jobId is invalid) remains undescribed.

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 resource definition before the chaining instructions, and every clause carries operational meaning. The trailing privacy/usage-tracking sentence is boilerplate that adds length without helping selection, though it is brief.

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 the description needn't enumerate return fields, and it still supplies the things the schema cannot: the null-feed state, pagination continuation, and the sibling call needed to act on results. An agent has everything required to call this correctly and interpret the response.

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 description coverage is only 33%, with just orgId documented, so the description carries the load: it explains jobId's provenance (from readJob) and cursor's contract (set to nextCursor when hasMore). Only orgId's multi-org semantics are left to the schema, which already covers 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?

Names a specific verb and resource ('List the people waiting on a role's Sourcing feed') and then defines the resource precisely: people the sourcing run approved but has not contacted, newest first, each with a 0-100 fit and a one-line reason. That level of scope definition makes it distinguishable from siblings like listRoleSearches or listProspects without opening any 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?

Explicitly routes the agent: use readJob to obtain jobId, use setRoleSearchDecision to pass or reach out (which starts outreach), and call again with nextCursor when hasMore is true. It also gives the negative-state signal (roleSearchId is null when no feed), so the agent knows when this tool has nothing to offer.

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