Skip to main content
Glama

PostWire

Publish a post now

post_to_social
Destructive

Publishes a post immediately and publicly to the listed platforms through the social accounts connected to the user's PostWire account. A published post cannot be withdrawn from PostWire. Accepts one text for all platforms or a separate per_platform draft for each. YouTube requires video_url; TikTok requires video_url or photos (photo_url or media); Instagram requires a photo or video, and two or more media items make a carousel. Every platform must already be connected; otherwise nothing is published and the error names the missing ones. The same payload sent twice within 2 minutes is refused as a duplicate unless idempotency_key differs. When a platform is connected in more than one brand and brand_id is omitted, nothing is published and the error lists the brands. Returns { posted, published_to, results: [{ platform, ok, id?, url?, account?, error? }] }, where account and published_to name the handle and brand each post went to; when the monthly post limit stops a platform, the result also names the plan that raises it, its price and a checkout link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoPost text used for every platform that has no per_platform draft.
mediaNoSeveral images (or images and videos) in one post, in order: an Instagram carousel (up to 10), TikTok photo post (up to 35 JPEG/WebP images), Bluesky (up to 4 images), Mastodon (up to 4), LinkedIn (up to 20 images, or one PDF document). Networks that take one item get the first. Each item: { url, type: image|video|document, alt? }.
titleNoTitle, used by YouTube.
privacyNoYouTube visibility. Default: the platform's default.
brand_idNoWhich brand's accounts to use. Omit to use the default brand.
photo_urlNoPublic https URL of an image.
platformsYesPlatforms to publish to, all in one call, e.g. ["linkedin","bluesky"].
video_urlNoPublic https URL of a video. Required for YouTube; TikTok takes a video or photos.
per_platformNoPer-platform drafts: { "<platform>": { "text": "…", "title": "…", "tags": ["…"] } }.
idempotency_keyNoOptional unique key; a repeat with the same key within 24 h is refused instead of posted twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / media
      Added value: +{
      +  "description": "Several images (or images and videos) in one post, in order: an Instagram carousel (up to 10), TikTok photo post (up to 35 JPEG/WebP images), Bluesky (up to 4 images), Mastodon (up to 4), LinkedIn (up to 20 images, or one PDF document). Networks that take one item get the first. Each item: { url, type: image|video|document, alt? }.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "alt": {
      +        "description": "Alt text (used by Bluesky, Mastodon and LinkedIn).",
      +        "maxLength": 1500,
      +        "type": "string"
      +      },
      +      "title": {
      +        "description": "Document title, used by LinkedIn.",
      +        "maxLength": 200,
      +        "type": "string"
      +      },
      +      "type": {
      +        "description": "Default image.",
      +        "enum": [
      +          "image",
      +          "video",
      +          "document"
      +        ],
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Public https URL of the file.",
      +        "format": "uri",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 35,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / properties / video_url / description
      Previous value: -"Public https URL of a video. Required for TikTok and YouTube."New value: +"Public https URL of a video. Required for YouTube; TikTok takes a video or photos."
  2. Changed3 schema fields changed
    • changedInput schema / properties / brand_id / description
      Previous value: -"Which brand's accounts to use, from my_account.brand_list. Omit to use the default brand."New value: +"Which brand's accounts to use. Omit to use the default brand."
    • changedInput schema / properties / per_platform / description
      Previous value: -"Per-platform drafts, as returned by generate_posts: { \"<platform>\": { \"text\": \"…\", \"title\": \"…\", \"tags\": [\"…\"] } }."New value: +"Per-platform drafts: { \"<platform>\": { \"text\": \"…\", \"title\": \"…\", \"tags\": [\"…\"] } }."
    • changedInput schema / properties / title / description
      Previous value: -"Title, used by YouTube (and Reddit)."New value: +"Title, used by YouTube."
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only indicate a destructive, non-read-only operation, so the description carries the behavioral burden. It adds irreversibility, fail-closed behavior when platforms are missing or brand_id is ambiguous, duplicate-payload refusal, and the monthly-limit upgrade response. This goes well beyond what annotations provide.

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 description is long, but it earns its length given 10 parameters and complex cross-platform rules. The main action and irreversibility are front-loaded, and while the dense clauses could be bulleted, there is little filler.

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?

With no output schema, the description compensates by documenting the exact return shape, error cases, brand ambiguity, connection prerequisites, and plan-upgrade details. An agent has enough information to invoke the tool correctly and interpret failures.

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?

Schema coverage is 100%, but the description adds platform-specific meaning not inferable from the schema alone: YouTube requires video_url, TikTok accepts video_url or photos, Instagram carousels need two or more media items, and idempotency is tied to same-payload detection. It also clarifies the single-text versus per_platform draft model.

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 action and resource: 'Publishes a post immediately and publicly to the listed platforms' through connected PostWire accounts. It distinguishes itself from sibling scheduling tools by emphasizing immediate publication and irreversibility.

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?

The description gives clear context for when to call it: platforms must already be connected, one text can be shared or per-platform drafts used, and media requirements differ by platform. It does not explicitly name schedule_post as the alternative for delayed publishing, but 'immediately' and 'cannot be withdrawn' make the intended use clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.