Skip to main content
Glama

LinkedIn: List user relations

linkedin_list_user_relations
Read-onlyIdempotent

List a LinkedIn user's visible relations by provider user ID. Use when network graph context is requested for a known profile.

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": {
      "user_id": "<user_id>"
    },
    "name": "linkedin_list_user_relations"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
searchNo
user_idYesStable LinkedIn system user ID returned by a profile/person resolver. Never pass a name or linkedin.com/in/... URL. LinkedIn system user ID: Stable LinkedIn user id, commonly ACo... for Classic profiles. Obtain with: linkedin_get_profile_from_url(profile_url) -> result.id; linkedin_get_profile(user_id_or_public_identifier) -> result.id; linkedin_search_people(...) -> selected result.id Never pass: full linkedin.com/in/... URL, person name, company ID.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / user_id / description
      Previous value: -"Stable LinkedIn system user ID returned by a profile/person resolver. Never pass a name or linkedin.com/in/... URL. LinkedIn system user ID: Stable LinkedIn/Unipile user id, commonly ACo... for Classic profiles. Obtain with: linkedin_get_profile_from_url(profile_url) -> result.id; linkedin_get_profile(user_id_or_public_identifier) -> result.id; linkedin_search_people(...) -> selected result.id Never pass: full linkedin.com/in/... URL, person name, company ID."New value: +"Stable LinkedIn system user ID returned by a profile/person resolver. Never pass a name or linkedin.com/in/... URL. LinkedIn system user ID: Stable LinkedIn user id, commonly ACo... for Classic profiles. Obtain with: linkedin_get_profile_from_url(profile_url) -> result.id; linkedin_get_profile(user_id_or_public_identifier) -> result.id; linkedin_search_people(...) -> selected result.id Never pass: full linkedin.com/in/... URL, person name, company ID."
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds one useful nuance beyond that — 'visible' relations, implying results are subject to the profile's visibility/privacy settings rather than being exhaustive. It says nothing about result volume, pagination via the cursor parameter, or rate limiting, so it stops short of rich behavioral context.

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?

Two sentences, no filler, with the operation stated before the usage hint — properly front-loaded. It is arguably undersized for a tool with four parameters and many near-identical siblings, but nothing written is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 is the only place the return shape could be explained, and it says nothing about what a 'relation' record contains or whether results are paginated. Combined with two undocumented parameters and a dense field of LinkedIn list-* siblings, an agent has real gaps to fill before calling this correctly.

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 50%: user_id and account_id are documented at length in the schema, but 'cursor' and 'search' have no description anywhere. The description's 'by provider user ID' merely restates the schema's user_id guidance and does not compensate for the undocumented pagination and filtering parameters. Baseline 3 is appropriate since the schema carries the critical parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'List' and the target 'a LinkedIn user's visible relations' are stated, and 'by provider user ID' scopes it to a specified profile rather than the caller. However, 'relations' is undefined terminology that does not map cleanly onto any sibling (linkedin_list_my_connections, linkedin_list_followers, linkedin_list_following), so an agent cannot tell what entity set will come back or how this differs from those tools.

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?

'Use when network graph context is requested for a known profile' gives an implied trigger condition, which is more than nothing. But there are no exclusions or named alternatives — nothing says to use linkedin_list_my_connections for the caller's own network or list_followers/list_following for direction-specific edges, which are the most likely confusions given the sibling set.

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.