Reach MCP — LinkedIn for AI agents

get_invitation_status

Read-onlyIdempotent

Get the connection and invitation status between the connected account and a LinkedIn member. Returns is_connection, invitation_type (SENT/PENDING/WITHDRAWN/REFUSED). Use before send_invitation or send_message to know the relationship (connected, invitation pending, refused). Read-only, cheap.

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": {
      "account_id": "<account_id>",
      "linkedin_id_or_url": "<linkedin_id_or_url>"
    },
    "name": "get_invitation_status"
  }
}

Input Schema

Name	Required	Description	Default
`account_id`	Yes	Reach id of the LinkedIn account to act on, from list_accounts.
`linkedin_id_or_url`	Yes	The LinkedIn member: profile URL, vanity name (the part after /in/), Sales Navigator URL, or internal member id.

Output Schema

Name	Required	Description
`degree`	No	Connection distance (1, 2 or 3).
`invitation_id`	No	Invitation URN, if any.
`is_connection`	No	True if the member is a 1st-degree connection.
`invitation_type`	No	'SENT' (pending sent), 'PENDING' (received, awaiting acceptance), 'WITHDRAWN', or 'REFUSED'.
`invitation_secret`	No	Shared secret, required to accept a received invitation.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds value on top by enumerating the returned status values (is_connection, SENT/PENDING/WITHDRAWN/REFUSED) and flagging the call as cheap, which helps an agent decide to probe it freely.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose, then return shape, then usage. No filler, and the most decision-relevant guidance (when to call) is present without padding.

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?

An output schema exists, so return-value documentation is not required in the description; the brief enumeration of status values is a bonus. For a two-parameter read tool with full annotation coverage, nothing an agent needs to select or invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%: account_id and linkedin_id_or_url are both documented in the schema, including accepted URL/vanity/id formats. The description adds no parameter detail beyond that, so the baseline 3 applies.

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+resource (get invitation status / connection status) and scopes it precisely: the relationship between the connected account and a given LinkedIn member. It is immediately distinguishable from siblings like list_sent_invitations or list_received_invitations, which enumerate rather than resolve one member's state.

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 names the decision point: 'Use before send_invitation or send_message to know the relationship (connected, invitation pending, refused).' It names two concrete alternative tools and the condition that selects this one, leaving nothing to inference.

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

All Reach MCP — LinkedIn for AI agents 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.

Resources

Need Help?