Skip to main content
Glama

rc_save_to_project

Save to Project in Recruiter Lite. Requires a LinkedIn Recruiter Lite seat and Linked API's Plus plan. Use personUrl from recruiterProfileUrl in rc_search_people or rc_retrieve_project_candidates, or personRecruiterUrl in get_inbox. Use projectId from rc_retrieve_projects or rc_create_project. Safe to repeat. Final result: { alreadyInProject }, true when the candidate was already saved and nothing changed.

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

Input Schema

NameRequiredDescriptionDefault
personUrlYesRecruiter profile URL (/talent/profile/…) of the candidate to save to this project
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?

Annotations only say readOnlyHint=false and openWorldHint=true; the description adds far more — that work is queued into a cloud-browser workflow taking minutes, the immediate pending snapshot shape, the pendingReason meanings ('queued' vs 'outsideWorkingHours'), and that working-hours parking may persist to the next business day. It also discloses idempotency ('Safe to repeat', alreadyInProject) and the duplicate-work hazard of retrying.

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?

Purpose and prerequisites are front-loaded, then return-value contract, then workflow mechanics — a sensible ordering. It runs long and portions about pending/workflow behavior are generic boilerplate that likely repeats across many siblings, but for an async queued mutation each sentence carries real operational weight.

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?

There is no output schema, and the description compensates fully by describing both the immediate `{status, pendingReason, workflowId, operationName, message}` response and the final `{alreadyInProject}` result shape. Prerequisites, idempotency and the follow-up retrieval step are all covered, so an agent can call and complete the task from this text alone.

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 already 100% with pattern and description for both parameters, so the baseline is 3. The description adds genuine value by specifying the upstream source fields for each argument (recruiterProfileUrl, personRecruiterUrl, projectId tools), which the schema does not say.

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 ('Save to Project in Recruiter Lite') and immediately names the scoping context (Recruiter Lite seat, Plus plan). It is clearly distinct from siblings like rc_create_project and rc_retrieve_project_candidates, which are referenced only as value sources.

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 tells the agent where each argument comes from (personUrl from recruiterProfileUrl in rc_search_people/rc_retrieve_project_candidates, or personRecruiterUrl from get_inbox; projectId from rc_retrieve_projects/rc_create_project). It also gives the critical when-not rule: 'Do not retry the original tool while a workflow is still running; that creates duplicate queued work,' plus routing to get_workflow_result for the final answer.

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.