Taplio for LinkedIn

Create draft

create_draft

Create a new LinkedIn post draft (unpublished). Attach media by passing media_ids (from list_media, or a media_id from create_media_upload_url whose bytes you have uploaded). Publish it later with schedule_draft or publish_draft.

Input Schema

Name	Required	Description
`content`	No	The text body of the LinkedIn post draft. 1 to 3000 characters.
`media_ids`	No	Optional ids of media to attach — from list_media (already uploaded) or from create_media_upload_url after you PUT the bytes. Referenced by id only.
`document_title`	No	Optional title LinkedIn shows for a PDF attached via media_ids in this same call. Defaults to the PDF file name. Ignored if no PDF is attached in this call. Up to 100 characters; letters, digits, spaces and hyphens are kept.

Output Schema

Name	Required	Description	Default
`id`	Yes
`media`	No
`status`	Yes
`content`	Yes
`created_at`	Yes
`updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026
- addedOutput schema / properties / updated_at
```
Added value: +{
+  "$ref": "#/properties/created_at"
+}
```

Changed2 schema fields changedOct 26, 2026

addedInput schema / properties / document_title

Added value: +{
+  "description": "Optional title LinkedIn shows for a PDF attached via media_ids in this same call. Defaults to the PDF file name. Ignored if no PDF is attached in this call. Up to 100 characters; letters, digits, spaces and hyphens are kept.",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}

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

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the record is created in an unpublished state, media must already be uploaded before its id is usable, and the draft requires a separate publish/schedule step to become live.

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?

Three short sentences with the core create action front-loaded, followed by the media attachment mechanics and the follow-up path. Nothing is padded and no sentence repeats another.

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 annotations cover the safety profile, so the description does not need to explain return values. The one gap is that no parameters are marked required in the schema and the description never clarifies whether content is effectively mandatory, which matters for an agent assembling the call.

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 description coverage is 100%, including the maxLength on content and the document_title semantics, so the schema already carries the parameter burden. The description's media guidance ('from list_media, or a media_id from create_media_upload_url whose bytes you have uploaded') largely restates what the media_ids schema description already says, so it adds little beyond baseline.

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+resource ('Create a new LinkedIn post draft') and immediately qualifies the resulting state as '(unpublished)', which cleanly separates it from publish_draft and schedule_draft in the sibling list.

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?

It names the downstream alternatives explicitly ('Publish it later with schedule_draft or publish_draft') and lays out the media prerequisite chain via list_media or create_media_upload_url. It stops short of stating when to use update_draft versus creating a new draft, so it is clear context rather than a full when/when-not matrix.

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.