Taplio for LinkedIn

List posts

list_posts

Read-onlyIdempotent

List the user's LinkedIn posts, newest first: posts created in Taplio (status scheduled, sending, or sent) plus posts published directly on LinkedIn, which always come back as sent. A draft becomes a post once it is scheduled or published. Taplio posts are ordered by when they were created in Taplio, posts published directly on LinkedIn by when they went live. With status scheduled and from or to set, the window applies to the scheduled date and posts come back soonest first. LinkedIn-native coverage is the last 90 days and relies on a daily sync, so a post published in the last few hours may not be listed yet. Engagement metrics are not included: use get_post_analytics for impressions, likes, comments and shares. Also useful before drafting, to avoid repeating recent topics and match the user's established voice. media_type reports each post's format (text, image, video, document or article; absent when the format cannot be determined). media lists the post's images, video or document as durable urls, for posts created in Taplio and posts published directly on LinkedIn. It can be empty even when media_type reports an image, video or document, when Taplio does not hold a copy of that media yet: do not call again to wait for it, describe the post from its text and media_type.

Input Schema

Name	Required	Description
`to`	No	Only posts on or before this date (YYYY-MM-DD or ISO 8601 datetime, UTC). With status scheduled the date is when the post is scheduled to go out; otherwise it is when a Taplio post was created, or when a post published directly on LinkedIn went live.
`from`	No	Only posts on or after this date (YYYY-MM-DD or ISO 8601 datetime, UTC). With status scheduled the date is when the post is scheduled to go out; otherwise it is when a Taplio post was created, or when a post published directly on LinkedIn went live.
`limit`	No	Max posts to return. Defaults to 25, capped at 100.
`cursor`	No	Pagination token from a previous response; omit for the first page.
`status`	No	Filter by status: scheduled (queued), sending (publishing now), or sent (live, including posts published directly on LinkedIn). scheduled and sending only ever match posts created in Taplio. Omit for all three.

Output Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

changedInput schema / properties / from / description

Previous value: -"Only posts on or after this date (YYYY-MM-DD or ISO 8601 datetime, UTC)."New value: +"Only posts on or after this date (YYYY-MM-DD or ISO 8601 datetime, UTC). With status scheduled the date is when the post is scheduled to go out; otherwise it is when a Taplio post was created, or when a post published directly on LinkedIn went live."

changedInput schema / properties / to / description

Previous value: -"Only posts on or before this date (YYYY-MM-DD or ISO 8601 datetime, UTC)."New value: +"Only posts on or before this date (YYYY-MM-DD or ISO 8601 datetime, UTC). With status scheduled the date is when the post is scheduled to go out; otherwise it is when a Taplio post was created, or when a post published directly on LinkedIn went live."

Changed1 schema field changedOct 26, 2026
- addedOutput schema / properties / items / items / properties / media / items / properties / title
```
Added value: +{
+  "description": "Document title shown on LinkedIn. Only set for documents.",
+  "type": "string"
+}
```
First observedOct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations: ordering rules, date-window semantics under status=scheduled, LinkedIn-native 90-day coverage with daily-sync lag, and a clear warning not to retry for empty media. These details materially affect how an agent interprets results.

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?

Front-loads the core listing behavior and scope, and most sentences carry operational value. It is somewhat long and spends multiple sentences on output caveats, but the structure remains purposeful rather than 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?

Complete for a complex listing tool: annotations cover safety and idempotence, the output schema covers returns, and the description fills key operational gaps around ordering, sync lag, draft exclusion, and media interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters. The description still adds value by explaining the interaction between status=scheduled and from/to, including that the date window shifts to scheduled date and results come back soonest first.

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?

States a specific verb and resource plus scope: the user's LinkedIn posts, newest first, including Taplio-created and LinkedIn-native posts. It also distinguishes posts from drafts and from engagement analytics, so an agent can identify the tool without opening the schema.

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?

Explicitly routes metrics requests to get_post_analytics and gives a proactive use case before drafting. It implies drafts are handled by list_drafts but does not name get_post or list_drafts as alternatives, leaving some sibling routing implicit.

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.