Skip to main content
Glama

List rated connections

connections_list
Read-only

Lists loaded LinkedIn connections excluding removed or skipped entries, with optional tier or reason filters and pagination. Read-only; does not contact LinkedIn.

Instructions

Returns one page of the loaded connections that have no removed or skipped state, optionally only one tier or one reason: name, position, company, connected on, tier, reason and URL. It changes nothing and does not contact LinkedIn.

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

Input Schema

NameRequiredDescriptionDefault
tierNoOnly this tier.
limitNoRows to return, 1 to 100.
offsetNoRows to skip.
reasonNoOnly this reason code, for example pitch, sales, empty, low, mission, thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds useful non-annotation context: results are a single page, removed/skipped connections are excluded, and the exact field set returned is listed. 'It changes nothing and does not contact LinkedIn' partly restates the annotations, which keeps this below a 5.

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 tightly packed sentences with the resource, scope, filters, and field list front-loaded; nothing is padding. The clause 'It changes nothing and does not contact LinkedIn' is largely redundant against the read-only and closed-world annotations, costing it a point.

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 four optional parameters, no output schema, and a simple read-only profile, the description supplies what the structured data cannot: which records are excluded and what fields come back. Ordering, total-count behavior, and the exact filter-combination rules are not covered, but those are minor for a paged list tool.

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%, and the schema already documents tier ('Only this tier'), reason, limit, and offset thoroughly, so the baseline is 3. The description's 'one page' and 'optionally only one tier or one reason' reinforce pagination and filtering intent but add no syntax, format, or interaction details beyond the schema, and the 'one tier or one reason' phrasing is slightly ambiguous about whether both filters can be combined.

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 gives a specific verb and resource ('Returns one page of the loaded connections') and enumerates the returned fields (name, position, company, connected on, tier, reason, URL). It also states a scope qualifier — records with no removed or skipped state — which an agent can use to distinguish it from sibling list tools. It stops short of naming any sibling, which keeps it from a 5.

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?

Usage is implied through the filters ('optionally only one tier or one reason') and the exclusion of removed/skipped connections, so an agent can infer this is the general rated-connections listing. There is no explicit when-to-use versus when-not-to-use statement, and siblings such as connections_check_list or connections_next are not referenced, leaving the routing decision to inference.

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