Skip to main content
Glama
Sign In

Linked API

by io.github.Linked-API
OverviewDiscussionsAdmin

retrieve_performance

Read-only

Allows you to retrieve performance analytics from your LinkedIn dashboard (st.retrievePerformance action).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint: discloses that the call is queued into a cloud-browser workflow, may take minutes, returns immediately with a status snapshot, and enumerates the pending reasons with their distinct consequences. The 'outsideWorkingHours' case even prescribes reporting the window to the user rather than looping — exactly the kind of behavior an agent could not infer from annotations.

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?

Three tight paragraphs: purpose, workflow mechanics, then pending-state semantics — well front-loaded with no filler. Slightly long for a no-arg tool, but every sentence carries an actionable constraint (no duplicate retries, when get_workflow_result returns immediately).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description closes the important gaps by describing the immediate response envelope (status, pendingReason, workflowId, operationName, message) and the handoff to get_workflow_result. It never says what analytics are actually returned or over what time window, which for a zero-arg analytics tool leaves the agent guessing about scope.

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?

Zero parameters, so there is no schema semantics to add and the baseline applies. The description helpfully names the underlying action (st.retrievePerformance), which aids mapping but is not parameter meaning.

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?

Specific verb+resource: 'retrieve performance analytics from your LinkedIn dashboard', plus the underlying action name (st.retrievePerformance). It does not, however, distinguish itself from siblings like retrieve_ssi or retrieve_profile_viewers, which plausibly overlap with 'performance analytics' — an agent cannot tell from this text which of the three surfaces which metrics.

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 clear operational routing: call this, then call get_workflow_result with the returned workflowId and operationName, and explicitly do NOT retry the original tool while a workflow is running. The gap is selection guidance — nothing says when to pick this over retrieve_ssi/retrieve_profile_viewers or execute_custom_workflow.

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

All Linked API toolsInspect
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.

Resources