Skip to main content
Glama

linkedin_list_connections

Read-onlyIdempotent

List your LinkedIn connections, newest first (LinkedIn's "recently added"), each with first and last name, headline, public profile id and URL, and when you connected. Pass since (an ISO date) to get only the people who connected from then on, e.g. this week's new connections. names_included=false means LinkedIn answered without names.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum connections to return
sinceNoOnly connections made at or after this ISO date or time, e.g. 2026-11-02
cursorNoPagination cursor from previous response
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
from_account_idNoWhich of the workspace's LinkedIn accounts to act as (its id from channels.list). Connections, invitations and search results are that person's own network. OMIT to use the default LinkedIn account (in a LinkedIn conversation, the account that conversation belongs to); pass it whenever the workspace has more than one. An account this workspace cannot use is refused, never swapped for another.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "Only connections made at or after this ISO date or time, e.g. 2026-11-02",
      +  "type": "string"
      +}
  2. Added
  3. Removed
  4. Added
  5. Removed
  6. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description is free to add things they can't: the sort order, the exact shape of each returned record, and the edge case that `names_included=false` means LinkedIn answered without names. It doesn't mention pagination behaviour explicitly, which would have raised this further.

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

Conciseness4/5

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

Three sentences, front-loaded with the core verb and resource, then the parameter hint, then the edge case. Every sentence carries information; the `names_included` clause is terse but earns its place as a response caveat.

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?

There is no output schema, so the description usefully compensates by listing the returned fields and the `names_included` flag. The multi-account semantics of `from_account_id` are left entirely to the schema, but that parameter is thoroughly documented there, so nothing critical 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%, so `limit`, `since`, `cursor`, `in_workspace` and `from_account_id` are already fully documented. The description restates the ISO-date meaning of `since` without adding syntax or constraints beyond the schema, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource ("List your LinkedIn connections") plus the ordering rule ("newest first", tied to LinkedIn's own "recently added" label) and enumerates the fields returned. That clearly separates it from an invitations-sent listing, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Offers implied usage guidance through the `since` example ("this week's new connections"), which shows a real use case. It gives no when-not-to-use guidance, no prerequisites, and never routes the agent to an alternative for adjacent tasks like sent invitations.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.