Socialync

publish_x_article_now

Destructive

Publish a native X ARTICLE immediately -- the long-form rich-text format with a headline, NOT a regular post. If the user has switched on the publish confirmation dialog in Socialync settings (off by default) and their client supports MCP elicitation, Socialync shows the user a confirmation dialog with the headline and body before publishing (a decline comes back as success false with consent "declined"; never retry it; no answer within 40 seconds counts as the chat confirmation). On other clients there is NO dialog. Either way, before calling, show the user the exact headline and full body and get their explicit confirmation in chat, the same way you would before sending an email on their behalf. Returns the article id and the URL of the seed post that announces it. The user's connected X account must have an X Premium subscription (any tier) -- without it X refuses with a 403 at publish time. Supported markdown: # ## ### headings, bold, italic, - bullet and 1. numbered lists, > blockquotes, links. Images: a cover via coverImageUrl, or via coverMediaId for an image uploaded with create_media_upload and finalize_media_upload, and an image inside the body on its own line as caption (JPG, PNG or WEBP, up to 20 images including the cover; Socialync copies them into its own storage when the draft is made). Tables and code blocks degrade to plain text. To publish later, pass scheduledFor to create_x_article_draft and approve it; Socialync publishes it at that time. Articles count toward the same 10/day cap as posts.

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": {
      "title": "<title>",
      "markdown": "<markdown>"
    },
    "name": "publish_x_article_now"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	The article headline, plain text (no markdown).
`markdown`	Yes	The article body as markdown. Put each image on its own line as ![caption](https://...). See the tool description for the supported subset.
`profileId`	No	The Socialync profile whose X account to publish from. Call list_profiles to see the profiles you can post to. Required only when this connection is authorized for more than one profile.
`coverMediaId`	No	Optional cover image already in Socialync: the mediaId of ONE image from finalize_media_upload or list_media (e.g. "upload:abc123"). Use it for a cover you uploaded with create_media_upload. Pass only one of coverImageUrl and coverMediaId.
`coverImageUrl`	No	Optional cover image: a public https URL to a JPG, PNG or WEBP.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

addedInput schema / properties / coverMediaId

Added value: +{
+  "description": "Optional cover image already in Socialync: the mediaId of ONE image from finalize_media_upload or list_media (e.g. \"upload:abc123\"). Use it for a cover you uploaded with create_media_upload. Pass only one of coverImageUrl and coverMediaId.",
+  "type": "string"
+}

Changed2 schema fields changedNov 5, 2026

addedInput schema / properties / coverImageUrl

Added value: +{
+  "description": "Optional cover image: a public https URL to a JPG, PNG or WEBP.",
+  "format": "uri",
+  "type": "string"
+}

changedInput schema / properties / markdown / description

Previous value: -"The article body as markdown. See the tool description for the supported subset."New value: +"The article body as markdown. Put each image on its own line as ![caption](https://...). See the tool description for the supported subset."

First observedOct 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Far beyond the annotations (destructiveHint/openWorldHint), it discloses the elicitation dialog path, that a decline surfaces as success false with consent 'declined' and must never be retried, that 40 seconds of silence counts as chat confirmation, image copying into Socialync storage, markdown degradation for tables/code, and the shared 10/day cap. That is exactly the operational context an agent needs for an irreversible publish.

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?

Front-loaded with the core action and the not-a-post distinction, then layered constraints. It is dense and mostly earns its length, but the confirmation-dialog paragraph (settings toggle, client support, decline semantics, 40-second timeout) is verbose and slightly repetitive with the later 'show the user... get explicit confirmation' sentence.

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?

Covers the full lifecycle for a destructive, open-world publish: prerequisites, consent flow, return values ('article id and the URL of the seed post'), media handling, and rate limits. No output schema exists, yet the description still states what comes back.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds real meaning by enumerating the supported markdown subset, requiring images on their own line as ![caption](url), listing accepted formats and the 20-image limit including the cover. It stops short of clarifying profileId selection beyond what the schema already says.

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?

States a specific verb and resource ('Publish a native X ARTICLE immediately') and immediately disambiguates from a regular post and, by mentioning scheduledFor/create_x_article_draft, from the draft path. An agent can pick this over publish_now or create_x_article_draft without opening any schema.

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?

Gives explicit when-to-use (immediate publish), explicit alternative (create_x_article_draft with scheduledFor + approve to publish later), and a hard prerequisite ('X Premium subscription... without it X refuses with a 403 at publish time'). It also prescribes the pre-call confirmation step and its fallback behavior.

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

All Socialync tools Inspect

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.