Skip to main content
Glama

rc_retrieve_projects

Read-only

Retrieve Projects in Recruiter Lite. Requires a LinkedIn Recruiter Lite seat and Linked API's Plus plan. Final result: an array of active projects with projectId, name, createdAt, candidateCount and projectUrl. Pass projectId to the project tools.

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results, 1–1000, default 25

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Well beyond the readOnlyHint/openWorldHint annotations, it discloses that execution is asynchronous, the exact shape of the immediate pending response, the meaning of each pendingReason value, and the duplicate-work consequence of retrying. This is exactly the context an agent needs to avoid misinterpreting a queued response as a failure.

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 result shape before the workflow mechanics, and each paragraph covers a distinct concern (result, async mechanics, pending reasons). The async section is lengthy and slightly repetitive about get_workflow_result, but no sentence is truly disposable.

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 no output schema, the description compensates by enumerating returned fields, and it fully covers the non-obvious async lifecycle, prerequisite licensing, and parked-workflow edge case. Nothing an agent needs in order to call this and interpret the response is missing.

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?

Only one parameter, and the schema already documents it fully (1–1000, default 25). The description never mentions 'limit' or the default page size, so it adds nothing beyond the schema; baseline 3 applies at 100% coverage.

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 ('Retrieve Projects in Recruiter Lite') and enumerates the returned fields (projectId, name, createdAt, candidateCount, projectUrl), so the agent knows exactly what it gets. It does not explicitly contrast with the nearest sibling, rc_retrieve_project_candidates, leaving the projects-vs-project-candidates boundary to be inferred from the noun.

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?

Gives prerequisites (Recruiter Lite seat, Linked API Plus plan), a downstream routing rule ('Pass projectId to the project tools'), and an explicit when-not ('Do not retry the original tool while a workflow is still running') with the correct alternative named (get_workflow_result). It also tells the agent what to do in the outsideWorkingHours case rather than looping.

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.