Skip to main content
Glama
Sign In
LinkedIn MCP Server

LinkedIn MCP Server

by Sabari2005
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

linkedin_respond_to_invitation

Accept or ignore incoming LinkedIn connection invitations by identifying the sender via name or public identifier.

Instructions

Accept or ignore a received connection invitation. Identify the sender by name or public identifier — the invitation list reorders between calls, so indexes are not used.

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": {
      "person": "<person>",
      "action": "<action>"
    },
    "name": "linkedin_respond_to_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes"accept" connects; "ignore" declines silently.
personYesSender name or public identifier, e.g. "Jane Doe" or "jane-doe-123".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses a useful behavioral trait—invitation list reordering—which explains why indexes are not used. It complements annotations by emphasizing non-read-only, non-idempotent operation without contradicting them.

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?

Two concise sentences, front-loaded with the core action, followed by a key usage warning. Every word earns its place with no waste.

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?

For a simple two-parameter tool with full schema descriptions and no output schema, the description is adequate. It covers the operation, identification method, and a behavioral caveat, making it complete for the task.

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 coverage is 100%, so baseline 3 is appropriate. The description adds minimal extra meaning beyond the schema, only reinforcing that person is a name or public identifier. No additional parameter semantics are provided.

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?

The description clearly states the tool accepts or ignores a received connection invitation, using specific verbs and a clear resource. It distinguishes itself from sibling tools like send_connection_request and withdraw_invitation by focusing on responding to received invitations.

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 provides clear context: use for received invitations, identify by name or public identifier. It does not explicitly mention alternatives or exclusions, but the 'invitation list reorders' note guides usage effectively.

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

Deploy Server

Other Tools