Taplio for LinkedIn

List connection requests

list_connection_requests

Read-onlyIdempotent

List every connection request this account has queued, newest first, whatever became of each one: pending while it waits in the send queue, sent once it left, failed or cancelled with the reason otherwise. Read this before asking to connect with a batch of people — anyone already listed as pending, sent or skipped does not need a second request. Covers requests queued from anywhere in Taplio, not just the ones sent through this tool. Returns the most recent requests only, up to 100; to check one specific person whatever their age, use get_connection_request.

Input Schema

Name	Required	Description	Default
`limit`	No	Max connection requests to return, newest first. Defaults to 25, capped at 100.

Output Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedOutput schema / properties / items / items / properties / skipped_reason
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / items / items / properties / status / enum

Previous value: -[
-  "pending",
-  "sent",
-  "failed",
-  "cancelled"
-]New value: +[
+  "pending",
+  "sent",
+  "skipped",
+  "failed",
+  "cancelled"
+]

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and closed-world behavior, but the description adds meaningful lifecycle states, reason reporting for failed or cancelled requests, cross-Taplio scope, ordering, and the 100-item cap. The only small ambiguity is that 'skipped' appears in the duplicate-avoidance sentence without being included in the earlier status list.

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?

The description is front-loaded and every sentence serves a purpose: lifecycle states, duplicate avoidance, cross-Taplio scope, and the alternative tool. It is slightly verbose but not padded.

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?

With an output schema present, the description does not need to explain return fields. It provides enough context about ordering, statuses, scope, cap, and when to use the sibling tool to call 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 100%, and the limit parameter is already fully described in the input schema. The description restates the newest-first ordering and 100-item cap but does not add parameter semantics beyond what the schema provides.

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 gives a specific verb and resource: list connection requests for the account, newest first, with status context. It also distinguishes the tool from get_connection_request by scoping this one to recent bulk listing versus checking one specific person.

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

Usage Guidelines5/5

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

It explicitly says to read this before sending a batch of connection requests so already pending, sent, or skipped people are not re-requested. It also names get_connection_request as the correct alternative for checking one specific person regardless of age.

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

All Taplio for LinkedIn tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.