Linked API

retrieve_profile_viewers

Read-only

Retrieves the people who recently viewed the current account's LinkedIn profile (st.retrieveProfileViewers action). Each entry is either identified — carrying name, publicUrl and urn (a member URN urn:li:member:, null when LinkedIn does not expose it) — or anonymous, carrying only the description line LinkedIn displayed and a searchUrl holding the criteria it disclosed; pass that searchUrl to search_people as customSearchUrl to look for the viewer. Viewers are ordered newest first, and viewedAt is an estimate derived from the relative age LinkedIn shows.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of viewers to retrieve (default 20).
`since`	No	ISO 8601 timestamp. Only viewers seen at or after it are returned, and reading stops once older views are reached. Matched against the estimated viewedAt.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses that actions are queued into a cloud-browser workflow, may take minutes, return an immediate {status, pendingReason, workflowId, operationName, message} envelope, and that retrying creates duplicate queued work. It also explains the two pendingReason values ('queued' vs 'outsideWorkingHours') and how polling differs for each.

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 resource and return-entry shape, then the async workflow contract, then pending states in priority order. It is fairly long and the workflow paragraph is generic boilerplate shared across all Linked API actions, with slight redundancy about long-polling snapshots, but every section carries actionable information.

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 still specifies the two entry shapes (identified with name/publicUrl/urn, anonymous with description/searchUrl), ordering, and the asynchronous result envelope. An agent has everything needed to call it and to resolve the eventual result.

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 both params are already documented. The description adds genuine context by explaining that viewers are ordered newest first and that viewedAt is an estimate derived from the relative age LinkedIn shows — which qualifies how `since` filtering behaves — but it does not touch `limit`.

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 — retrieves people who recently viewed the current account's LinkedIn profile — and even cites the underlying action (st.retrieveProfileViewers). It is unmistakably distinct from data-fetching siblings like retrieve_connections or search_people.

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 routes the agent: pass an anonymous entry's searchUrl to search_people as customSearchUrl, and use get_workflow_result with the returned workflowId/operationName to obtain the result. It also states an exclusion — do not retry the original tool while a workflow is running — and tells the agent to report the working-hours window to the user rather than looping.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Linked API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.