Skip to main content
Glama

Publish & Cross-Post Across 18 Social Networks

posts_publish

Publish immediately (publish_now), schedule for a future ISO-8601 timestamp (schedule), enqueue into the profile slot queue (queue), or simultaneously cross-post (cross_post) content and media across 18+ social networks. Includes the built-in X Smart Link Optimizer (xLinkStrategy: 'first_reply'), which automatically strips external links from the main X post and publishes them in an immediate 1st reply—cutting X API link costs by 85% ($0.03 vs $0.20) while avoiding main-feed link reach penalties. Returns the persisted postId, per-platform delivery receipts (platformResults), total API cost (totalCostUsd), and exact dollar savings (totalSavedViaSmartLinkUsd).

Input Schema

NameRequiredDescriptionDefault
actionYesPublishing mode: 'publish_now' dispatches immediately, 'cross_post' syndicates tailored variants across multiple networks at once, 'schedule' holds until `scheduledFor`, and 'queue' places the post in the next best engagement slot.
contentYesPrimary post body text, caption, or thread hook. May include hashtags, mentions, and URLs (external URLs on X are automatically handled according to `xLinkStrategy`).
platformsYesNon-empty array of destination social network slugs to publish or cross-post to (e.g. `['x', 'linkedin', 'bluesky', 'threads']`).
profileIdNoBrand profile identifier (`prof_...`) whose connected social accounts will publish the post.prof_allometrik
scheduledForNoOptional ISO-8601 UTC or offset timestamp (e.g. '2026-10-27T08:30:00+01:00') specifying when a scheduled post should go live.
mediaAssetIdsNoOptional list of Nuntior media asset IDs (`med_...`) from `media_pipeline` to attach as images, carousels, or videos.
xLinkStrategyNoX (Twitter) link optimization mode: 'first_reply' moves any URL to an automated 1st reply to save $0.17/post (85% X API cost reduction) and maximize organic impressions; 'inline' leaves the URL in the main tweet; 'bio' replaces the URL with a bio pointer.first_reply
autoAdjustMediaNoWhen true, automatically selects the matching aspect-ratio variant (9:16 for Reels/TikTok/Shorts, 16:9 or 1:1 for X/LinkedIn) for each target platform.
authModeOverrideNoOptional authentication override forcing delivery through 'managed' Nuntior OAuth credentials or 'byok' customer-supplied keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / action / description
      Added value: +"Publishing mode: 'publish_now' dispatches immediately, 'cross_post' syndicates tailored variants across multiple networks at once, 'schedule' holds until `scheduledFor`, and 'queue' places the post in the next best engagement slot."
    • addedInput schema / properties / authModeOverride / description
      Added value: +"Optional authentication override forcing delivery through 'managed' Nuntior OAuth credentials or 'byok' customer-supplied keys."
    • addedInput schema / properties / autoAdjustMedia / description
      Added value: +"When true, automatically selects the matching aspect-ratio variant (9:16 for Reels/TikTok/Shorts, 16:9 or 1:1 for X/LinkedIn) for each target platform."
    • changedInput schema / properties / content / description
      Previous value: -"Post text (may include URLs to optimize on X)"New value: +"Primary post body text, caption, or thread hook. May include hashtags, mentions, and URLs (external URLs on X are automatically handled according to `xLinkStrategy`)."
    • addedInput schema / properties / mediaAssetIds / description
      Added value: +"Optional list of Nuntior media asset IDs (`med_...`) from `media_pipeline` to attach as images, carousels, or videos."
    • addedInput schema / properties / platforms / description
      Added value: +"Non-empty array of destination social network slugs to publish or cross-post to (e.g. `['x', 'linkedin', 'bluesky', 'threads']`)."
    • changedInput schema / properties / platforms / items / enum
      Previous value: -[
      -  "x",
      -  "linkedin",
      -  "instagram",
      -  "facebook",
      -  "threads",
      -  "tiktok",
      -  "youtube",
      -  "bluesky",
      -  "mastodon",
      -  "farcaster",
      -  "reddit",
      -  "pinterest",
      -  "google_business",
      -  "telegram",
      -  "discord",
      -  "ghost",
      -  "wordpress",
      -  "webflow"
      -]New value: +[
      +  "x",
      +  "linkedin",
      +  "bluesky",
      +  "instagram",
      +  "facebook",
      +  "threads",
      +  "tiktok",
      +  "youtube",
      +  "reddit",
      +  "pinterest",
      +  "mastodon",
      +  "telegram",
      +  "discord",
      +  "google_business",
      +  "ghost",
      +  "wordpress",
      +  "webflow",
      +  "whatsapp"
      +]
    • addedInput schema / properties / profileId / default
      Added value: +"prof_allometrik"
    • addedInput schema / properties / profileId / description
      Added value: +"Brand profile identifier (`prof_...`) whose connected social accounts will publish the post."
    • changedInput schema / properties / scheduledFor / description
      Previous value: -"ISO-8601 timestamp when scheduling"New value: +"Optional ISO-8601 UTC or offset timestamp (e.g. '2026-10-27T08:30:00+01:00') specifying when a scheduled post should go live."
    • changedInput schema / properties / xLinkStrategy / description
      Previous value: -"Moves links on X to 1st reply to save $0.17/post ($0.20 -> $0.03 or $0 BYOK) and boost reach."New value: +"X (Twitter) link optimization mode: 'first_reply' moves any URL to an automated 1st reply to save $0.17/post (85% X API cost reduction) and maximize organic impressions; 'inline' leaves the URL in the main tweet; 'bio' replaces the URL with a bio pointer."
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

The description provides rich behavioral detail beyond the standard hints, especially regarding the `xLinkStrategy`. It explains the economic and functional benefits of link optimization (85% cost reduction, avoiding reach penalties), offering critical context for decision-making.

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 definition is highly dense but logically structured, front-loading the primary function and then detailing complex, high-value features (X Link Optimization and return values) efficiently.

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?

The tool is complex (18 platforms, scheduling, media, optimization, authentication). The description covers every major functional area, ensuring an agent has complete context before attempting an invocation.

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?

Even with 100% schema coverage, the description adds high semantic value by clarifying the operational difference between the `action` enum modes and explaining the specific implications of using the `xLinkStrategy` parameter.

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 clearly defines the tool's purpose as publishing and cross-posting across 18+ social networks, which is highly specific. It immediately distinguishes itself from other potential publishing tools by specifying its scope and modes of operation.

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?

It provides explicit usage guidelines by defining four distinct operational modes (`publish_now`, `schedule`, `queue`, `cross_post`) and explaining the specific conditions under which each mode should be invoked.

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.

Resources