Skip to main content
Glama

Draft posts for each platform

draft_posts
Read-only

Use this when the user wants social posts written about a topic, such as "write posts about our new CLI for X, Bluesky and LinkedIn". Pass the topic, with every fact and any link to include, and 1 to 6 platforms from x, bluesky, threads, mastodon, linkedin, instagram, reddit, youtube, pinterest, tiktok; optionally a tone. Returns one draft per platform with its length as that platform counts it, hashtags, whether it passes the platform's rules and the issues if not, plus a checklist of rules and image sizes with sources and dates. Uses only the facts given. It does not publish, read accounts or fetch trends or statistics.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "The launch of our new open-source CLI, branch-tidy. It deletes merged git branches in one command, works on macOS, Linux and Windows, and is MIT licensed.",
      "platforms": [
        "x",
        "bluesky",
        "linkedin"
      ]
    },
    "name": "draft_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoOptional voice, such as "friendly and plain" or "dry humour".
topicYesWhat the posts are about, with any facts, names and link to include. Posts use only what is given here.
platformsYesWhere the posts will go, up to 6 of x, bluesky, threads, mastodon, linkedin, instagram, reddit, youtube, pinterest, tiktok.

Output Schema

NameRequiredDescriptionDefault
as_ofYes
draftsYes
noticeYes
sourceYes
statusYes
messageNo
checklistYes
rules_as_ofYesDate the platform rules were last checked (2026-10-01).
ai_disclosureYesSet when the topic or a draft declares an AI-generated person or voice; names the label that applies on X, Instagram, TikTok and YouTube drafts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "platforms": [
      +      "x",
      +      "bluesky",
      +      "linkedin"
      +    ],
      +    "topic": "The launch of our new open-source CLI, branch-tidy. It deletes merged git branches in one command, works on macOS, Linux and Windows, and is MIT licensed."
      +  }
      +]
  2. Changed1 schema field changed
    • removedOutput schema / properties / note_from_openkrill
      Removed value: -{
      -  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedOutput schema / properties / note_from_openkrill
      Added value: +{
      +  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, non-idempotent), the description adds real behavioral context: it 'uses only the facts given' (no external grounding or invention), never publishes or reads accounts, and returns rule-compliance issues plus a rules-and-image-sizes checklist with sources and dates. That is substantive disclosure the structured fields do not carry.

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 trigger and example, then parameters, then return shape and limits – a logical order. It is somewhat long and repeats the full platform list that already lives in the schema enum, which is wasted space.

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 3-parameter generation tool with an output schema and annotations, everything an agent needs is present: trigger condition, input grounding rule, platform constraints, return payload composition, and explicit non-capabilities. Nothing material is missing.

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 schema already documents topic, platforms and tone. The description nonetheless reinforces the critical semantic that the topic must contain every fact and link because generation is grounded solely in it, which is a meaningful constraint beyond the schema text. The repeated platform enumeration is the only redundancy.

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?

The description opens with a concrete trigger ('when the user wants social posts written about a topic') and an example, then names the exact output unit: one draft per platform with length, hashtags and rule-pass status. It is clearly separable from siblings like draft_video_script or draft_tiktok_slides, which target different artifacts.

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?

It states the use case, gives a literal user-request example, and draws explicit negative boundaries: 'does not publish, read accounts or fetch trends or statistics.' An agent knows both when to call it and what it cannot do, which is the strongest form of routing guidance.

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.