Skip to main content
Glama
MahbbRah

SocialDispatch MCP Server

by MahbbRah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

publish_social_post

Publish a post immediately to one or more connected social accounts, including remote media URLs or local files, so content can be shared across platforms from one request.

Instructions

Publish a social post immediately across one or more connected social accounts in SocialDispatch. Supports remote media URLs or local file paths directly.

Input Schema

NameRequiredDescriptionDefault
tagsNoKeywords/tags for video discovery (supported on YouTube SEO).
titleNoVideo title for platforms requiring dedicated titles (e.g. YouTube). Max 100 characters. If omitted, falls back to the first line of content.
contentNoText caption/content of the post (or video description on YouTube)
isShortNoExplicitly designate video as a YouTube Short (appends #Shorts to title and formats link as youtube.com/shorts/...). If omitted, auto-detected from aspect ratio and duration.
linkUrlNoOptional URL for link preview card
mediaUrlsNoOptional array of publicly accessible image or video URLs to attach (or local file paths, which will be automatically uploaded)
accountIdsYesList of connection IDs to publish to (obtained via list_social_connections)
mediaFilesNoOptional array of local file paths on disk (e.g. ["/path/to/video.mp4"]) to upload directly to SocialDispatch storage and attach to post
thumbnailUrlNoOptional public image URL to use as custom video thumbnail (supported for YouTube, Facebook, and TikTok; JPEG/PNG recommended max 2MB for YouTube, up to 10MB for Facebook)
privacyStatusNoVideo privacy visibility (supported on YouTube, defaults to "public").
thumbnailFileNoOptional local file path to a custom thumbnail image on disk (e.g. "/path/to/thumb.jpg") to automatically upload and set for YouTube, Facebook, or TikTok videos
tiktokThumbnailNoAlias for thumbnailFile/thumbnailUrl: custom thumbnail image path or URL for TikTok video uploads
variantContentsNoOptional dictionary of platform-specific or account-specific text overrides (e.g. {"facebook": "...", "x": "..."})
youtubeThumbnailNoAlias for thumbnailFile/thumbnailUrl: custom thumbnail image path or URL for video uploads
facebookThumbnailNoAlias for thumbnailFile/thumbnailUrl: custom thumbnail image path or URL for Facebook video uploads

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries the full behavioral burden. It discloses two useful traits beyond the schema: publishing is immediate (no scheduling) and local file paths are auto-uploaded rather than rejected. It omits what an agent most needs for a multi-platform write: failure semantics (does one failed account abort the rest?), whether posts are live/public immediately and how to undo, and any rate or size limits.

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?

Two tight sentences with the core action front-loaded and the media note second. Nothing is wasted, though the second sentence largely restates schema content rather than adding decision-relevant information.

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?

For a 15-parameter, multi-platform, nested-object publishing tool with no annotations and no output schema, the description is thin: it says nothing about the result (per-account outcomes/IDs), partial-failure behavior, or platform-specific constraints. The rich schema compensates for parameter-level gaps, but the operational picture is incomplete.

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 coverage is 100%, so the schema already explains all 15 parameters in detail, including aliases and platform support. The description only echoes the media-URL/local-path distinction already documented in mediaUrls and mediaFiles, adding no syntax or precedence guidance (e.g. when to use mediaUrls vs mediaFiles).

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 (publish) and resource (social post) plus scope: one or more connected accounts in SocialDispatch. The word 'immediately' implicitly distinguishes it from schedule_social_post, but no sibling is named, so differentiation is only implied.

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?

Usage is only inferable from 'publish ... immediately' – an agent can guess this is the now-path versus schedule_social_post or generate_and_publish_post, but the description never says so, nor does it state prerequisites such as requiring connected accounts or that content/media must satisfy per-platform rules.

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

Deploy Server

Other Tools