Skip to main content
Glama

rc_retrieve_project_candidates

Read-only

Retrieve Project Candidates in Recruiter Lite. Requires a LinkedIn Recruiter Lite seat and Linked API's Plus plan. Use projectId from rc_retrieve_projects or rc_create_project. Omit stage to read all stages. Final result: an array of candidates with name, recruiterProfileUrl, headline, location, avatarUrl, viewerState.connectionDegree and stage.

Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work.

A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.

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": {
      "projectId": "<projectId>"
    },
    "name": "rc_retrieve_project_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results, 1–1000, default 25
stageNo
projectIdYesProject ID as a string of digits from rc_retrieve_projects or rc_create_project

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the queued cloud-browser execution model, the immediate pending snapshot shape ({status, pendingReason, workflowId, operationName, message}), and the meaning of pendingReason values 'queued' and 'outsideWorkingHours'. The working-hours case even tells the agent to stop polling and report the window to the user, which is behavioral context 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?

Front-loaded with the core action and parameter source, then the async-workflow mechanics. It is longer than most definitions and the duplicate-work warning is stated twice in spirit, but nearly every sentence carries operational value for an asynchronous tool.

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 an async, no-output-schema tool, the description covers the return contract (final candidate array fields), the interim pending contract, and the handoff tool for completion. Nothing an agent needs in order to call it and handle the response 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 67%; the description adds meaning for stage ('omit to read all stages') and reinforces that projectId must be a digit string sourced from the project list/create tools. The limit parameter is only documented by the schema, but that documentation is adequate.

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 and resource ('Retrieve Project Candidates in Recruiter Lite') and scopes it to a project via projectId, which distinguishes it from the broader people-search siblings. It also enumerates the returned candidate fields, so the agent knows exactly what it gets.

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 names where projectId comes from (rc_retrieve_projects or rc_create_project), explains that omitting stage reads all stages, and routes the agent to get_workflow_result instead of retrying. It also gives a negative instruction ('Do not retry the original tool while a workflow is still running') with the reason (duplicate queued work).

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.