Skip to main content
Glama

Create Social Post

create_social_post
Destructive

[write] Create a DRAFT post (not live, never auto-published) on one social account (account_id or account_uuid); the result carries the post's id and uuid. platform = ig|fb|tw|tt|yt|li|th|tg|bsky. caption fills the platform's text field (ig_post_caption, fb_post_message, tw_post_text, tt_post_title, yt_post_description, li_post_text, th_post_text). fields = the rest of the /api//posts/create body with prefixed keys, e.g. ig: {ig_post_type: SINGLE|CAROUSEL|REELS, ig_post_items: [{type: IMAGE|VIDEO, url}]}; fb: {fb_post_type, fb_post_items, fb_post_link}; tw: {tw_post_type: TEXT|IMAGE|VIDEO|POLL, tw_post_items}; tt: {tt_post_type: VIDEO|PHOTO, tt_post_items, tt_post_privacy_level}; yt: {yt_post_title, yt_post_privacy_status, yt_post_made_for_kids, yt_post_video_url}; li: {li_post_type: TEXT|IMAGE|VIDEO|ARTICLE, li_post_items, li_post_article_url}; th (Threads, caption up to 500 chars): {th_post_type: TEXT|IMAGE|VIDEO|CAROUSEL, th_post_items: [{type: IMAGE|VIDEO, url, alt_text?}] (one for IMAGE/VIDEO, 2-20 for CAROUSEL), th_post_reply_control: everyone|accounts_you_follow|mentioned_only, th_post_topic_tag, th_post_link_attachment (TEXT only)}; bsky (Bluesky, caption up to 300 chars, published at once unless scheduled with schedule_social_post): {bsky_post_type: TEXT|IMAGE, bsky_post_items: [{url, alt?}] (1-4 images for IMAGE), bsky_post_langs: ["tr"]}; tg (a Telegram user account posting to its own channels/groups): {tg_post_type: TEXT|PHOTO|VIDEO|ALBUM, tg_post_items, tg_post_target_ids: [tg_target_id, 1-10 ACTIVE targets that can_post]} - caption is the text (4096 for TEXT, 1024 under media). Media items are public urls. Schedule fields are ignored here - use schedule_social_post after approval.

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": {
      "platform": "<platform>"
    },
    "name": "create_social_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
captionNo
platformYes
account_idNo
account_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only flag it as a non-idempotent, open-world, destructive write; the description adds the behavior that actually matters: the result is a draft carrying id and uuid, media must be public URLs, Threads caps captions at 500 chars, Bluesky at 300 and publishes immediately unless scheduled, Telegram requires 1-10 ACTIVE targets that can_post with 4096/1024 caption limits, and carousels need 2-20 items.

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 write/draft/return semantics before the per-platform detail, and nearly every clause carries needed information given the undocumented schema. It is nonetheless a dense semicolon-separated wall whose per-platform blocks are hard to scan quickly.

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 five-parameter tool with no output schema and 0% parameter documentation, the description covers what is created, what is returned, all per-platform field vocabularies and limits, and where scheduling belongs. Only minor gaps remain, such as whether account_id or account_uuid is required in practice.

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 description coverage is 0% and the schema puts no meaning on any of the five parameters, yet the description explains platform as a nine-value enum (ig|fb|tw|tt|yt|li|th|tg|bsky), maps caption onto each platform's concrete text field, defines fields as the remaining /api/<p>/posts/create body keys with per-platform key names and allowed values, and covers account_id vs account_uuid. This is far more value than the schema supplies.

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?

Uses a specific verb and resource plus a critical scope qualifier: creates a DRAFT post on ONE social account, not live and never auto-published, and returns the post's id and uuid. That distinguishes it immediately from publish_social_post and schedule_social_post in the sibling list.

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?

Explicitly states the draft-only condition ('not live, never auto-published'), tells the agent that schedule fields are ignored here, and routes scheduling to schedule_social_post after approval. The when/when-not split is unambiguous.

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