Skip to main content
Glama

rc_fetch_person

Read-only

Fetch Person 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. basicInfo defaults to true; recruitingActivity defaults to false. Final result: candidate profile fields including recruiterProfileUrl, publicUrl and industry, with optional recruitingActivity counts for projects, messages, feedback and attachments.

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>"
    },
    "name": "rc_fetch_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
basicInfoNoRead candidate details; SDK default true
personUrlYesRecruiter profile URL (https://www.linkedin.com/talent/profile/…) from recruiterProfileUrl in rc_search_people or rc_retrieve_project_candidates, or personRecruiterUrl in get_inbox; public /in/ URLs are not accepted
recruitingActivityNoRead recruiting activity; default false

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 claim readOnly and openWorld; the description goes far beyond by disclosing that actions are queued into a cloud-browser workflow, may take minutes, return a pending snapshot with status/pendingReason/workflowId, and must be resolved via get_workflow_result. It also explains the 'queued' vs 'outsideWorkingHours' pending reasons and the duplicate-work risk of retrying, none of which are inferable from structured fields.

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, prerequisites and input source, then the async mechanics, then the pending-reason edge cases — a sensible escalation of detail. It is long and there is some repetition between the workflow paragraph and the pendingReason paragraph, but each block covers a distinct failure mode an agent would otherwise hit.

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 supplies the shape of the final result (recruiterProfileUrl, publicUrl, industry, optional recruitingActivity counts) and fully covers the async lifecycle, prerequisites and edge cases. Nothing an agent needs in order to call this correctly or handle its 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 100%, so baseline is 3; the description adds value by restating the defaults (basicInfo true, recruitingActivity false), constraining the URL source, and explaining what recruitingActivity actually returns (project, message, feedback and attachment counts). It stops short of adding anything beyond that for the boolean flags, but the URL-provenance detail is genuinely useful.

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?

The opening sentence names a specific verb and resource (fetch a person) and pins the variant to Recruiter Lite, which separates it from the sibling fetch_person / nv_fetch_person tools. It also names the exact origin of the required URL (recruiterProfileUrl from rc_search_people or rc_retrieve_project_candidates, personRecruiterUrl from get_inbox), so an agent knows precisely where this tool fits.

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?

Explicit prerequisites (Recruiter Lite seat, Linked API Plus plan), explicit input sourcing from three named sibling tools, and an explicit prohibition: 'public /in/ URLs are not accepted'. It also tells the agent what to do after the call (use get_workflow_result) and what not to do (do not retry the original tool while a workflow is running).

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.