Skip to main content
Glama
Sign In

Posteady

by com.posteady
OverviewDiscussionsAdmin

Publish post(s) immediately

publish_post
Destructive

Immediately publish one or more text posts to Threads, X (Twitter), and/or LinkedIn accounts. Threads posts can carry images from the media library via mediaIds on the first post: one image, or 2–20 images as a carousel; all target accounts must then be Threads accounts. TikTok Business takes video with an uploaded mediaId, a requestId UUID, and explicit PUBLIC_TO_EVERYONE privacy, for exactly one account and one caption. TikTok video is processed asynchronously: get_publish_status tracks the returned jobId, and repeating a request with the same requestId returns the same job. Instagram takes instagram with one account, a requestId UUID, FEED (1–20 media items), REELS (1 item), or STORIES (1 item), and uploaded mediaIds; it cannot be combined with posts or video. Caption is optional except that STORIES rejects it, and shareToFeed is REELS-only. Instagram publishing is asynchronous. YouTube takes youtube with one account, a requestId UUID, an uploaded video mediaId, a title (1–100 characters), optional description, privacyStatus (public, unlisted, or private), and optional madeForKids; it cannot be combined with posts, video, or instagram. YouTube publishing is asynchronous: get_publish_status tracks the returned jobId, and repeating a request with the same requestId returns the same job. A Facebook Page takes facebook with one account, a requestId UUID, and explicit FEED, REELS, or STORY content type. FEED accepts text and up to 10 uploaded media items, REELS requires one video, and STORY requires one image or video and rejects message. Facebook publishing is asynchronous and reported by get_publish_status. Multiple posts are chained as a thread on Threads/X. LinkedIn is single-caption only — it does not support chaining, so sending more than one post to a LinkedIn account is rejected. Supports cross-posting to up to 5 accounts at once. For X, links (http://, https://, www., and bare domains such as foo.io/path) are automatically removed from posts[0] before publishing. Replies in posts[1+] and other platforms keep their links. Character limits apply after removal; an empty first X post rejects the entire request with VALIDATION_ERROR. Character limits: Threads 500, X 280 (25000 for Premium), LinkedIn 3000. The target workspace is determined automatically from accountIds (each account belongs to exactly one workspace); all accountIds must belong to the same workspace. ⚠️ This action is IRREVERSIBLE — posts are sent to the platform immediately.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountIds": "<accountIds>"
    },
    "name": "publish_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postsNoText posts to publish. Required for text and TikTok modes; omit for Instagram, YouTube, or Facebook. If multiple, they are published as a thread chain. Max 25 items. For X, links (http://, https://, www., and bare domains such as foo.io/path) are automatically removed from posts[0] before publishing. Replies in posts[1+] and other platforms keep their links. Character limits apply after removal; an empty first X post rejects the entire request with VALIDATION_ERROR.
videoNoTikTok Business video: an uploaded mediaId and a requestId UUID (a repeated requestId returns the same job). Requires exactly one account and one caption. Only PUBLIC_TO_EVERYONE is supported.
youtubeNoYouTube video: one account, a requestId UUID, an uploaded video mediaId, a title, optional description, privacyStatus public/unlisted/private, and optional madeForKids. Cannot be combined with posts, video, or instagram.
facebookNoFacebook Page post: one account, a requestId UUID, explicit FEED/REELS/STORY content type, optional FEED/REELS message, and uploaded media IDs. STORY does not accept message. Cannot be combined with posts, video, instagram, or youtube.
mediaIdsNoThreads only: image mediaIds from the media library (list_media with mediaType IMAGE, or uploaded images) attached to posts[0]. One image makes an image post; 2–20 images make a carousel. Replies in posts[1+] stay text. Every accountId must be a Threads account. Cannot be combined with video, instagram, youtube, or facebook.
instagramNoInstagram media post: one account, a requestId UUID, FEED/REELS/STORIES content type, and 1–20 uploaded media IDs. Cannot be combined with posts or video.
accountIdsYesAccount IDs to publish to (from list_accounts). 1–5 accounts. Each account ID must be a UUID.
workspaceIdNoOptional. The target workspace is determined automatically from accountIds; when given, it must match the accounts' workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / instagram / description
      Previous value: -"Instagram media post: one account, a requestId UUID, FEED/REELS/STORIES content type, and 1–10 uploaded media IDs. Cannot be combined with posts or video."New value: +"Instagram media post: one account, a requestId UUID, FEED/REELS/STORIES content type, and 1–20 uploaded media IDs. Cannot be combined with posts or video."
    • changedInput schema / properties / instagram / properties / items / description
      Previous value: -"Ordered media items. FEED accepts 1–10; REELS and STORIES require exactly 1."New value: +"Ordered media items. FEED accepts 1–20; REELS and STORIES require exactly 1."
    • changedInput schema / properties / instagram / properties / items / maxItems
      Previous value: -10New value: +20
  2. Changed1 schema field changed
    • addedInput schema / properties / mediaIds
      Added value: +{
+  "description": "Threads only: image mediaIds from the media library (list_media with mediaType IMAGE, or uploaded images) attached to posts[0]. One image makes an image post; 2–20 images make a carousel. Replies in posts[1+] stay text. Every accountId must be a Threads account. Cannot be combined with video, instagram, youtube, or facebook.",
+  "items": {
+    "format": "uuid",
+    "type": "string"
+  },
+  "maxItems": 20,
+  "minItems": 1,
+  "type": "array"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructive, openWorld, readOnly=false, and idempotent=false. The description adds substantial context beyond that: immediate delivery, irreversible publishing, link stripping on X, platform character limits, requestId idempotency for async modes, and job-based processing.

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?

The definition is lengthy, but the complexity of eight parameters and multiple publishing modes justifies much of it, and the purpose is front-loaded. Some platform field details duplicate the schema, but the dense constraint information generally earns its place.

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

Completeness5/5

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

For a complex multi-platform publishing tool with no output schema, the description covers supported modes, cross-parameter exclusions, async job tracking, workspace inference, character limits, and irreversible behavior. An agent has enough information to select the correct mode and avoid invalid combinations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is already 100%, the description adds cross-parameter meaning that field-level schema cannot express: mediaIds only attaches to Threads posts[0] and requires all accounts to be Threads, Instagram cannot combine with posts or video, and posts[1+] form thread replies. It also clarifies platform-specific mode constraints for TikTok, YouTube, Facebook, and LinkedIn.

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: immediately publish one or more text posts to Threads, X, and/or LinkedIn, then expands to supported media modes. It clearly distinguishes immediate publishing from siblings such as schedule_post and points to get_publish_status for asynchronous job tracking.

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 gives explicit mode-selection constraints: Instagram, YouTube, Facebook, and TikTok cannot be combined with posts, LinkedIn rejects chaining, and cross-posting is capped at five accounts. It also names get_publish_status for async tracking, though it does not explicitly route scheduled publishing to schedule_post.

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

All Posteady toolsInspect
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