Skip to main content
Glama
Sign In

LinkedIn MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Send connection invitation in LinkedIn

linkedin_send_connection_invitation
Read-onlyIdempotent

Send connection invitation in the user's own LinkedIn account from ChatGPT, Claude or any AI agent. Returns how to do it in LinkedIn step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's LinkedIn Cloud Browser. LinkedIn's official API: LinkedIn has an official API, but most of it needs an approved application (checked 6 Nov 2026).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with them, adding the concrete behavioral fact that nothing is opened or sent by the call itself. The trailing note about LinkedIn's official API requiring an approved application adds context about why the browser path is needed.

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

Conciseness3/5

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

The core flow is front-loaded and clear, but the final sentence about LinkedIn's official API and the '(checked 6 Nov 2026)' aside are tangential to calling the tool and dilute an otherwise tight description.

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 output schema, the description carries the burden of describing returns and does so at a high level (step-by-step screens, buttons, fields). Combined with the pointer to the browser tools needed to act on the output, an agent has enough to call it correctly, though the exact shape of the returned guide is not specified.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing in the schema the description needs to compensate for.

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?

The description states a specific outcome: it returns step-by-step instructions (screens, buttons, fields) for sending a LinkedIn connection invitation, and explicitly says it 'opens nothing by itself.' This corrects the impression created by the name 'send', so an agent can tell it is a guidance tool rather than an action tool, though the name/title still pull in the opposite direction.

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?

It gives a clear two-step flow: call this to get the procedure, then execute it with the cotlet_browser_* tools in the user's LinkedIn Cloud Browser. It does not name when-not-to-use or a sibling alternative (e.g. cotlet_app_guide), so it stops short of full routing guidance.

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

All LinkedIn MCP Server and API by Cotlet 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