SendIt

Publish Content

publish_content

Publish content to social media platforms.

MEDIA RULES: • mediaUrl must be a public HTTPS URL — NOT a local file path. • If the user shares an image/video in chat, call create_upload_session FIRST to get a browser upload link, then use the returned URL here. • Text-only works on: LinkedIn, Threads, X, Facebook. • Image required: Instagram, Pinterest. • TikTok supports one video or 1-35 Photo Mode images. • Video required: YouTube.

Call validate_content to check before publishing.

Input Schema

TableJSON Schema

Name	Required	Description
`content`	Yes
`team_id`	No	Team ID to publish as team. Get available teams with list_teams. If omitted, publishes from personal accounts.
`platforms`	Yes	Target platforms. Choose based on content type: text-only→LinkedIn/Threads/X, image→Instagram/Threads/Facebook/Pinterest/TikTok Photo Mode, video→Instagram/TikTok/Threads/YouTube

Output Schema

TableJSON Schema

Name	Required	Description	Default
`isError`	No
`results`	No
`success`	No
`errorMessage`	No
`totalPlatforms`	No
`followUpSuggestions`	No
`successfulPlatforms`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedMay 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "errorMessage": {
+      "type": "string"
+    },
+    "followUpSuggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "isError": {
+      "type": "boolean"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "error": {
+            "type": "string"
+          },
+          "platform": {
+            "enum": [
+              "x",
+              "linkedin",
+              "linkedin-page",
+              "facebook",
+              "instagram",
+              "threads",
+              "bluesky",
+              "mastodon",
+              "nostr",
+              "youtube",
+              "tiktok",
+              "lemmy",
+              "discord",
+              "slack",
+              "telegram",
+              "pinterest",
+              "dribbble",
+              "devto",
+              "hashnode",
+              "gmb",
+              "whop",
+              "producthunt"
+            ],
+            "type": "string"
+          },
+          "postId": {
+            "type": "string"
+          },
+          "postUrl": {
+            "type": "string"
+          },
+          "success": {
+            "type": "boolean"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "successfulPlatforms": {
+      "type": "number"
+    },
+    "totalPlatforms": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already disclose mutation via readOnlyHint=false, so the bar is lowered. The description adds valuable constraints: mediaUrl must be public HTTPS, chat-shared media requires an upload session, and certain platforms mandate specific media types. It does not describe post-publish effects (e.g., irreversibility), but this is not a major gap given the mutation annotation.

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?

The description is compact and front-loaded with a clear purpose. The bulleted MEDIA RULES are dense, each delivering a distinct actionable constraint, and the final 'Call validate_content' line is a useful pointer. No wasted words.

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?

Given the tool's complexity (22 platform enums, nested content object, output schema available), the description covers the most decision-critical aspects: media requirements, upload session dependency, and validation step. It omits details like publishing immediacy or required account connections, but the rich input schema and output schema compensate for these gaps.

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 67% and most content properties already have descriptions. The MEDIA RULES largely restate the schema's own platforms guidance (e.g., 'Text-only→LinkedIn/Threads/X'), and the upload session workflow is already embedded in the mediaUrl schema description. The description adds little new parameter meaning 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 opens with a specific verb and resource: 'Publish content to social media platforms.' The MEDIA RULES further clarify scope by detailing platform-specific requirements, distinguishing this from scheduling (schedule_content) or validation (validate_content) sibling tools.

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?

The description gives explicit procedural alternatives: 'If the user shares an image/video in chat, call create_upload_session FIRST' and 'Call validate_content to check before publishing.' It also provides when-to-use context via platform/media compatibility rules (text-only vs image vs video requirements).

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

All SendIt tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3/5.0

Disambiguation2/5

With 148 tools, there is significant overlap. For example, generate_content, publish_ai, generate_post_bundle, and request_project_content all generate content; get_analytics, get_unified_analytics, get_post_analytics, get_ad_performance, and get_unified_ad_report all fetch performance metrics; and list_inbox vs list_conversations blur comment and conversation management. Descriptions help, but boundaries between tools are often unclear.

Naming Consistency3/5

Most tools follow a verb_noun pattern (e.g., list_teams, create_goal, delete_post), but there are notable deviations: create_library_item vs save_to_library, publish_content vs publish_ai, schedule_content vs schedule_content_advanced, and connect_platform vs connect_connector. Mixed prefixes like 'autopilot_', 'check_', and 'get_' are fine, but overlapping verbs and a hyphen in 'connect_linkedin-page' reduce consistency.

Tool Count1/5

148 tools is extreme for any server. Even for a broad social media management platform, this is far beyond what an agent can effectively navigate. The count is unwieldy and suggests the surface should be split into multiple focused servers (publishing, analytics, connectors, workflows, etc.).

Completeness3/5

The core social publishing workflow is well covered (create, schedule, publish, edit, delete, retry), and there are extensive features for analytics, workflows, connectors, and AI agents. However, some resources have CRUD gaps: no update/delete for brand voices, no delete_project, no update/delete for Product Hunt goals, and no explicit get_workflow. These are workable but notable omissions.

Resources

Need Help?