Skip to main content
Glama
Sign In
LinkedIn MCP Server

LinkedIn MCP Server

by Sabari2005
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

linkedin_get_invitations

Read-onlyIdempotent

List pending LinkedIn connection invitations, including received and sent requests, with sender names and personalized messages.

Instructions

List pending connection invitations — either received (awaiting your response) or sent (awaiting theirs). Returns sender names and any personalised message.

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_get_invitations"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoDefaults to "received".
limitNoDefaults to 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read nature is covered. The description adds context about what is returned (sender names and personalized message) and clarifies the meaning of received vs. sent, adding value beyond the annotations.

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?

The description is a single sentence that is front-loaded with the main purpose and includes no fluff. Every word contributes to understanding the tool's function and return value.

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?

For a simple read-only list tool with only two params and no output schema, the description is complete. It covers what the tool does, what it returns, and the key distinction between received and sent invitations, leaving no critical gaps.

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% with both parameters documented (defaults for 'type' and 'limit'). The description adds some semantic context for the 'type' parameter (received vs. sent) but does not add syntax or format details beyond the schema, so the baseline of 3 is appropriate.

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 a specific verb and resource: 'List pending connection invitations'. It also distinguishes between received and sent invitations, making it distinct from sibling tools like linkedin_respond_to_invitation or linkedin_withdraw_invitation.

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?

The description implies when to use the tool: to view pending invitations, with the received/sent distinction. It does not explicitly name alternatives or exclusions, but the context of sibling tools makes the use case clear.

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