Skip to main content
Glama

Create Post Draft

autoposter_draft_post

Creates a draft post for human review. If API key lacks direct publish, post is saved as pending_approval and notifications are sent to workspace approvers. Accepts mediaUrls (public URLs) or files (client-supplied file objects up to 100MB). For large video files over 100MB, tell the user to provide a direct public file URL or use autoposter_get_media_upload_url.

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": {
      "accountIds": "<accountIds>",
      "content": "<content>"
    },
    "name": "autoposter_draft_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoOptional client-supplied file objects to attach to the post.
titleNoOptional title. Used by YouTube, Pinterest and WordPress; ignored elsewhere.
contentYesBase text content of the post.
mediaIdsNoOptional list of existing media IDs from workspace media library (from autoposter_list_media).
postTypeNoOptional target format where applicable: 'post' (default feed post/carousel), 'reel' (Instagram or Facebook Reel; requires video), 'story' (Instagram or Facebook 24h Story; requires image or video), or 'shorts' (YouTube Shorts; vertical video under 60s). Ignored on platforms without format variants.
mediaUrlsNoOptional public image or video URLs to attach (e.g. from autoposter_upload_media).
accountIdsYesList of account IDs from autoposter_list_accounts.
visibilityNoOptional audience for TikTok posts (default PUBLIC_TO_EVERYONE). Ignored on other platforms.
firstCommentNoOptional first comment posted on the post right after it publishes (e.g. links or hashtags). Supported on platforms with comment support such as X, Facebook, Instagram, LinkedIn, Threads, Bluesky, Mastodon, Telegram, Discord.
threadCommentsNoOptional thread: follow-up texts posted in order after publishing, each replying to the previous one. If firstComment is also set, these come after it. On X this makes a tweet thread.
platformContentNoOptional platform-specific content overrides (e.g. twitter, linkedin).

Output Schema

NameRequiredDescriptionDefault
messageYesStatus message indicating draft creation.
draftPostsYesList of created draft posts per account.
instructionsNoInstructions for approving or viewing the draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / firstComment
      Added value: +{
      +  "description": "Optional first comment posted on the post right after it publishes (e.g. links or hashtags). Supported on platforms with comment support such as X, Facebook, Instagram, LinkedIn, Threads, Bluesky, Mastodon, Telegram, Discord.",
      +  "type": "string"
      +}
    • addedInput schema / properties / threadComments
      Added value: +{
      +  "description": "Optional thread: follow-up texts posted in order after publishing, each replying to the previous one. If firstComment is also set, these come after it. On X this makes a tweet thread.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "Optional title. Used by YouTube, Pinterest and WordPress; ignored elsewhere.",
      +  "type": "string"
      +}
    • addedInput schema / properties / visibility
      Added value: +{
      +  "description": "Optional audience for TikTok posts (default PUBLIC_TO_EVERYONE). Ignored on other platforms.",
      +  "enum": [
      +    "PUBLIC_TO_EVERYONE",
      +    "SELF_ONLY",
      +    "MUTUAL_FOLLOW_FRIENDS"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / files / description
      Previous value: -"Optional files generated in chat or uploaded by user to attach to the post."New value: +"Optional client-supplied file objects to attach to the post."
  3. Changed1 schema field changed
    • addedInput schema / properties / platformContent / additionalProperties
      Added value: +{
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / postType
      Added value: +{
      +  "description": "Optional target format where applicable: 'post' (default feed post/carousel), 'reel' (Instagram or Facebook Reel; requires video), 'story' (Instagram or Facebook 24h Story; requires image or video), or 'shorts' (YouTube Shorts; vertical video under 60s). Ignored on platforms without format variants.",
      +  "enum": [
      +    "post",
      +    "reel",
      +    "story",
      +    "shorts"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / draftPosts / items / properties / postType
      Added value: +{
      +  "description": "Target format ('post', 'reel', 'story', or 'shorts').",
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "draftPosts": {
      +      "description": "List of created draft posts per account.",
      +      "items": {
      +        "properties": {
      +          "accountName": {
      +            "description": "Target account name.",
      +            "type": "string"
      +          },
      +          "id": {
      +            "description": "Draft post ID.",
      +            "type": "string"
      +          },
      +          "platform": {
      +            "description": "Target social media platform.",
      +            "type": "string"
      +          },
      +          "scheduledAt": {
      +            "description": "Scheduled timestamp if any.",
      +            "type": "string"
      +          },
      +          "status": {
      +            "description": "Current post status (drafts or pending_approval).",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "platform",
      +          "status"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "instructions": {
      +      "description": "Instructions for approving or viewing the draft.",
      +      "type": "string"
      +    },
      +    "message": {
      +      "description": "Status message indicating draft creation.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "message",
      +    "draftPosts"
      +  ],
      +  "type": "object"
      +}
  6. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=true; the description adds genuinely new behavioral facts: an approval-required fallback (pending_approval) when the API key lacks publish rights, and that approver notifications are dispatched. It also discloses the 100MB per-file ceiling, which is not in the schema.

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?

Three sentences, each carrying distinct information: purpose, approval behavior, media input rules plus the size edge case. The primary purpose is front-loaded and nothing is repeated from the schema verbatim.

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 an 11-parameter mutation tool with full schema coverage and an output schema, the description covers the risky/ambiguous parts: approval flow, media size limits, and where to go when media is too large. Return shape is handled by the output schema, so no significant agent-facing gap remains.

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, but the description adds real semantics the schema lacks: the tradeoff between mediaUrls and files, and the 100MB limit with the correct fallback path. Other 11 parameters (postType, visibility, threadComments, platformContent) are left entirely to the schema, which does document them well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Creates a draft post") and adds scope via "for human review", so the draft-vs-publish distinction is at least implied. It does not explicitly name the sibling it contrasts with (autoposter_publish_draft or autoposter_schedule_post), which keeps it from a 5.

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?

Gives a concrete routing rule for the oversized-media case: use a public file URL or call autoposter_get_media_upload_url. It also tells the agent how to behave ("tell the user") in that branch. Missing is explicit guidance on when to choose this over schedule_post or publish_draft.

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