Linked API

get_network

Read-only

Get connection events from the monitored network, newest first. Requires network monitoring to be enabled once with sync_network. Event types: "connectionAccepted" (a connection request you sent was accepted), "connectionAdded" (a new connection appeared in your network), "connectionRequestReceived" (someone sent you a connection request). Every event carries personUrn — the permanent LinkedIn member URN (urn:li:member:) of the person the event is about, or null when LinkedIn does not expose it or the event was recorded before URNs were captured.

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

Input Schema

Name	Required	Description	Default
`type`	No	Optional event type filter: "connectionAccepted", "connectionAdded", or "connectionRequestReceived". If omitted, all event types are returned.
`since`	No	Optional ISO 8601 timestamp to only retrieve events after this date (e.g., '2024-01-15T10:30:00Z'). If not provided, all captured events are returned.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only and open-world, but the description adds substantial non-obvious behavior: work is queued into a cloud-browser workflow, the call returns immediately with a pending snapshot, pendingReason values are decoded ('queued' vs 'outsideWorkingHours'), and it explains that 'outsideWorkingHours' returns immediately and should be surfaced to the user rather than polled.

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 and event taxonomy, then the async workflow protocol. Most sentences carry real information, though the workflow/pendingReason passage is long and reads like shared boilerplate that could be tightened without losing meaning.

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?

No output schema exists, yet the description documents the shape of the immediate return ({status, pendingReason, workflowId, operationName, message}), how to obtain final results, and the semantics of personUrn including its null case. An agent has everything needed to invoke and handle results correctly.

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 goes beyond the schema by defining each enum value in plain language ('connectionAccepted' = a connection request you sent was accepted, etc.) and by explaining the null case for the personUrn field on returned events.

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 ('Get connection events from the monitored network'), adds ordering ('newest first'), and enumerates the three event types, which cleanly separates it from siblings like retrieve_connections or retrieve_invitations that return static lists.

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 a clear prerequisite ('Requires network monitoring to be enabled once with sync_network') and an explicit follow-up path ('call get_workflow_result with the returned workflowId'), plus a negative instruction not to retry while a workflow is running. It does not explicitly contrast with the closest sibling (retrieve_connections / retrieve_invitations), which keeps it from a 5.

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.