Taplio for LinkedIn

Publish now

publish_draft

Destructive

Publish a LinkedIn post draft to LinkedIn immediately. This goes live now and cannot be undone.

Input Schema

Name	Required	Description	Default
`id`	Yes	The id of the draft to publish immediately (from list_drafts).

Output Schema

Name	Required	Description
`id`	Yes
`url`	Yes
`media`	No	Media attached to this post, for posts published through Taplio and directly on LinkedIn. `url` is a durable copy hosted by Taplio. Can be empty while `media_type` reports an image, video or document, when Taplio does not hold a copy of that media yet or can no longer recover it. Text and article posts return an empty array.
`status`	Yes
`content`	Yes
`metrics`	No
`sent_at`	No
`created_at`	Yes
`media_type`	No	Format of the post. Absent when the format cannot be determined.
`scheduled_for`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / media / items / properties / title

Added value: +{
+  "description": "Document title shown on LinkedIn. Only set for documents.",
+  "type": "string"
+}

First observedOct 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is known. The description adds real context beyond that: the post goes live publicly right now and the action cannot be undone, which is the key consequence an agent must weigh before calling.

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

Conciseness5/5

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

Two short sentences, purpose first, irreversible consequence second. No filler and nothing buried.

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?

An output schema exists and the single parameter is fully documented, so the description only needed to convey purpose and risk, which it does. Naming the scheduled alternative would have made it complete for a mutation tool with several sibling paths.

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?

Only one parameter, and the schema documents it fully (100% coverage) including its provenance from list_drafts. The description adds nothing about the id, so baseline 3 applies.

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 ('Publish a LinkedIn post draft to LinkedIn immediately'), so the agent knows exactly what operation occurs. It implicitly separates itself from schedule_draft via 'immediately', but never names that sibling, so it falls short of 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?

The word 'immediately' implies this is the non-scheduled path, and the irreversibility warning implies caution, but no alternative is named and no when-to-use/when-not-to-use rule is stated. The agent must infer the schedule_draft distinction on its own.

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.