Skip to main content
Glama

rc_search_people

Read-only

Search People in Recruiter Lite. Requires a LinkedIn Recruiter Lite seat and Linked API's Plus plan. Provide term, a nonempty filter, or customSearchUrl; a custom URL cannot be combined with term or filter. Filters alone are accepted; scope fields and false booleans alone are not search criteria. Final result: an array of candidates with name, recruiterProfileUrl, headline, location, avatarUrl and viewerState.connectionDegree.

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_search_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNo
limitNoMaximum results, 1–1000, default 25
filterNo
customSearchUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Well beyond the readOnlyHint/openWorldHint annotations, it discloses that actions are queued into a cloud-browser workflow, return immediately with {status, pendingReason, workflowId, operationName, message}, and may take minutes. The pendingReason semantics ('queued' vs 'outsideWorkingHours') and the duplicate-work warning are exactly the kind of behavior an agent cannot infer 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 the search-criteria contract before the async workflow mechanics, and each paragraph has a distinct job. It is dense and long, but the length is driven by a genuinely complex async contract rather than filler; a sentence or two could still be tightened.

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?

Covers the full lifecycle: eligibility, valid invocation shapes, immediate pending response, retrieval via get_workflow_result, working-hours parking behavior, and the final result fields despite there being no output schema. An agent has everything needed to call, poll correctly, and report status to a user.

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 only 25%, but the description compensates by explaining the mutual exclusivity of term/filter/customSearchUrl and the rule that scope fields and false booleans are not standalone criteria — semantics the schema does not encode. It also states the shape of returned candidates. It stops short of explaining limit or the many filter sub-fields, which the schema covers via enums.

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?

Opens with a specific verb and resource plus the product variant: "Search People in Recruiter Lite." The gating requirement (Recruiter Lite seat + Plus plan) further separates it from generic siblings like search_people or nv_search_people, though the description never explicitly says which alternative to use when the seat constraint fails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete invocation rules: supply term, a nonempty filter, or customSearchUrl; a custom URL cannot be combined with term or filter; filters alone are accepted; scope fields and false booleans alone are not criteria. It also states the operational rule not to retry while a workflow is running and to use get_workflow_result instead. Missing only an explicit statement of when to prefer this over the non-Recruiter-Lite search siblings.

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.