Socialync

create_x_article_draft

Hold a native X ARTICLE -- the long-form rich-text format with a headline, NOT a regular post -- as a pending draft WITHOUT publishing it. Pass scheduledFor to publish it later instead of right away. Show the user the headline, full body, images and time, and when they say yes in chat call approve_draft(draftId); never tell the user to open the Socialync app to approve it. Use publish_x_article_now instead when the user has already confirmed in chat and wants it out now. 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": "create_x_article_draft"
  }
}

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.
`scheduledFor`	No	Optional ISO 8601 UTC datetime to publish the article later (e.g. 2026-04-15T14:00:00Z). Must be in the future. Leave out to publish as soon as the user approves.
`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"
+}

Changed3 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."

addedInput schema / properties / scheduledFor

Added value: +{
+  "description": "Optional ISO 8601 UTC datetime to publish the article later (e.g. 2026-04-15T14:00:00Z). Must be in the future. Leave out to publish as soon as the user approves.",
+  "type": "string"
+}

First observedOct 12, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the non-destructive draft-creation profile is known. The description adds substantial context beyond them: the X Premium prerequisite causing a 403 at publish time, the 10/day cap shared with posts, image copying into Socialync storage, and markdown degradation rules. That is well above the annotation baseline.

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-loads the core action and the alternative-tool routing before the formatting and prerequisite details, so an agent can act on the first two sentences. It loses a point for duplication: the scheduledFor-to-publish-later rule is stated twice in near-identical terms.

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

Completeness4/5

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

For a six-parameter, annotation-covered, no-output-schema tool this covers the important ground — prerequisites, formatting contract, image handling, scheduling, and the approval handoff. The only soft spot is that the return value is only implied by the approve_draft(draftId) reference rather than stated explicitly.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: the supported markdown subset (# ## ###, bold, italic, bullets, numbered lists, blockquotes, links), the per-line image syntax, the 20-image cap, and the JPG/PNG/WEBP constraint. It also reinforces the scheduledFor-must-be-in-the-future semantics and the cover URL vs coverMediaId workflow.

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 — holding a native X ARTICLE as a pending draft — and explicitly contrasts it with 'a regular post' and with the sibling tool publish_x_article_now. An agent can distinguish this from create_post_draft or publish_x_article_now 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?

Names the exact routing conditions: use publish_x_article_now when the user has already confirmed and wants it out now; use approve_draft(draftId) after the user says yes in chat; pass scheduledFor for later publication. It even states a negative instruction — never tell the user to open the Socialync app to approve.

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.