Social Media MCP by Publinio

create_draft

Idempotent

Save a reviewable draft for a connected account, or supply platform to draft before connecting. Use existing media IDs. Does not publish or schedule. Reuse idempotencyKey on retry.

Input Schema

Name	Required	Description	Default
`brandId`	Yes
`content`	Yes
`platform`	No
`settings`	No
`connectionId`	No
`mediaAssetId`	No
`mediaAssetIds`	No
`idempotencyKey`	Yes

Output Schema

Name	Required	Description	Default
`id`	Yes
`status`	Yes
`content`	Yes
`brand_id`	Yes
`platform`	Yes
`revision`	Yes
`timezone`	Yes
`published_at`	Yes
`scheduled_at`	Yes
`approval_state`	Yes
`media_asset_id`	Yes
`media_asset_ids`	Yes
`platform_post_id`	Yes
`approval_required`	Yes
`approval_revision`	Yes
`social_account_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields changedOct 12, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "facebook",
-  "instagram",
-  "tiktok",
-  "youtube",
-  "linkedin",
-  "linkedin_company",
-  "x",
-  "threads",
-  "pinterest",
-  "wordpress",
-  "bluesky",
-  "reddit"
-]New value: +[
+  "facebook",
+  "instagram",
+  "tiktok",
+  "youtube",
+  "linkedin",
+  "linkedin_company",
+  "x",
+  "threads",
+  "pinterest",
+  "wordpress",
+  "bluesky",
+  "reddit",
+  "telegram",
+  "mastodon"
+]

addedInput schema / properties / settings / properties / mastodon_settings

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "language": {
+          "maxLength": 40,
+          "type": "string"
+        },
+        "mediaDescriptions": {
+          "items": {
+            "maxLength": 1500,
+            "type": "string"
+          },
+          "maxItems": 4,
+          "type": "array"
+        },
+        "sensitive": {
+          "type": "boolean"
+        },
+        "spoilerText": {
+          "maxLength": 10000,
+          "type": "string"
+        },
+        "visibility": {
+          "enum": [
+            "public",
+            "unlisted",
+            "private",
+            "direct"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "visibility",
+        "spoilerText",
+        "sensitive",
+        "language",
+        "mediaDescriptions"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed3 schema fields changedOct 8, 2026

removedInput schema / properties / content / minLength
```
Removed value: -1
```

addedInput schema / properties / settings / properties / instagram_share_to_feed

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / properties / settings / properties / publishing_format

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "post",
+        "reel",
+        "story"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare non-destructive, idempotent, closed-world. The description adds genuine value beyond them: 'Use existing media IDs' (no upload path), 'Does not publish or schedule' (write but not live), and 'Reuse idempotencyKey on retry' (how to leverage idempotency). It omits auth/permission needs and error behavior.

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?

Four short sentences, zero filler, and the key facts (save draft, platform fallback, no publish, retry with same key) are front-loaded. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema means return values need no explanation, and the description covers the non-publishing semantics well. However, for a tool with a deep nested settings object at 0% schema coverage, the description gives an agent no guidance on which settings apply to which platform, leaving a meaningful gap.

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 0%, so the description must compensate. It gestures at idempotencyKey, media IDs, platform, and connected account, but explains nothing about brandId, content, or the large nested settings object (30+ platform-specific fields). Partial compensation only.

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 names a specific verb+resource ('save a reviewable draft') and immediately carves out scope with 'Does not publish or schedule,' which cleanly separates it from siblings like schedule_post and cancel_post. An agent can tell exactly what this tool produces.

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 states two concrete usage modes (connected account vs. draft-before-connecting by supplying platform) and an explicit exclusion ('Does not publish or schedule'). It stops short of naming the alternative sibling tools to call for publishing/scheduling, so it is clear but not fully routing.

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

All Social Media MCP by Publinio 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.

Resources

Need Help?