Skip to main content
Glama

Social0

create_draft

Create an unpublished Social0 draft (does not post to any network). Use when the user wants to write content first and publish/schedule later. For one-step live posting use publish_now. Example: 'Draft a LinkedIn post about AI.'

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": {
      "content": "<content>",
      "platforms": "<platforms>"
    },
    "name": "create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaNoMedia upload IDs from upload_media
contentYesPost caption / text content
platformsYesPlatform names (linkedin, twitter_x, etc.) or connected account UUIDs
platform_optionsNoAdvanced per-platform settings. Supports content/caption and media per platform, plus pinterest board_id/title/link/create_board, tiktok title/privacy/draft/comment/duet/stitch/commercial/AI flags, instagram cover_image_url/trial_reel, youtube title, and x/twitter_x madeWithAi/paidPartnership.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/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 safety is partly covered; the description still earns credit for clarifying the key side-effect question — that creating a draft does not publish to any network. It stops short of covering auth/account requirements, whether duplicate drafts are created on retry (idempotentHint=false), or what the call returns (e.g. a draft ID).

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?

Three short sentences, front-loaded with the scope-defining parenthetical, then usage routing, then an example. The example sentence is mildly redundant with the usage sentence but does demonstrate intent mapping, so it mostly earns its place.

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 non-idempotent mutation with a nested platform_options object and no output schema, the description covers the main agent needs: what it creates, that it does not publish, and which alternative to pick. The one notable gap is that it never says the result includes a draft identifier that later update_draft/publish calls require.

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

Parameters3/5

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

Schema description coverage is 100%, so content, platforms, media and the nested platform_options are already well documented in the schema, and the baseline of 3 applies. The description adds no parameter-level meaning such as platform-name format expectations or how media IDs are obtained, leaving that entirely to the schema text.

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 ("Create an unpublished Social0 draft") and immediately bounds the scope with "(does not post to any network)". It then names the sibling it is not (publish_now), so an agent can distinguish the two without opening either 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 an explicit when-to-use ("user wants to write content first and publish/schedule later") and an explicit when-not with the alternative named ("For one-step live posting use publish_now"). The example utterance further anchors the intent that should route here.

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.