Reach MCP — LinkedIn for AI agents

send_invitation

Send a connection request to a LinkedIn member. Optional message capped at 300 chars (premium) or 200 chars. Use to connect with someone not yet a 1st-degree connection; check get_invitation_status first to avoid duplicates. Counts against the daily invitations quota; for more than ten use create_job. To follow without connecting use follow_member.

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

Input Schema

Name	Required	Description
`message`	No	Optional personalised invitation note.
`account_id`	Yes	Reach id of the LinkedIn account to act on, from list_accounts.
`idempotency_key`	No	Optional. A key you choose (a UUID is fine) that names this exact call. If you retry with the same key and the same arguments, the first call's result is returned and nothing is done twice on LinkedIn. Reusing a key with different arguments is refused. Keys expire after 24 hours.
`linkedin_id_or_url`	Yes	LinkedIn member ID, vanity name, or profile URL.

Output Schema

Name	Required	Description	Default
`connected`	No	Invitation sent

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 8, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations cover only the safety profile (readOnly=false, openWorld, non-idempotent, non-destructive); the description adds real behavioral context the annotations cannot convey: the daily invitation quota, the duplicate risk, and the 300/200-char message caps. It omits any mention of the schema's idempotency_key retry semantics and of permission/failure behavior, so it stops short of a 5.

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?

Four dense sentences, front-loaded with the core action and followed by constraints, prerequisites, and alternatives. Every sentence carries actionable information with no filler.

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 values need not be explained. Combined with 100% schema parameter coverage and annotations carrying the safety profile, the description supplies everything else an agent needs: quota, rate/alternatives, duplicate avoidance, and message limits.

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 a 3 baseline applies; the description adds meaning beyond the schema by specifying the message length limit (300 premium / 200 chars), which the schema only calls an 'optional personalised invitation note'. No other parameter gets added semantic detail, keeping it below 5.

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 ('Send a connection request to a LinkedIn member') and immediately scopes it to non-1st-degree connections. It explicitly distinguishes itself from sibling tools, naming follow_member for the no-connection case and create_job for bulk outreach, so an agent can route correctly without opening other schemas.

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?

Gives explicit when-to-use ('connect with someone not yet a 1st-degree connection'), a prerequisite ('check get_invitation_status first to avoid duplicates'), and two alternatives with their selecting conditions ('for more than ten use create_job'; 'To follow without connecting use follow_member'). Nothing about selection is left 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?