Skip to main content
Glama

Create a post draft

create_post_draft

Create a content plan so the swarm can produce assets for it. Nothing is published by this tool.

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": {
      "name": "<name>",
      "objective": "<objective>",
      "strategy_campaign_id": "<strategy_campaign_id>"
    },
    "name": "create_post_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
objectiveYes
platformsNo
project_idNo
target_audienceNo
strategy_campaign_idYesThe 12-stage planner campaign this content comes from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare non-destructive and non-idempotent behavior, so the bar is lower. The description adds real context beyond them: nothing is published and the swarm consumes the plan to produce assets downstream, which hints at asynchronous follow-on work. It still omits duplicate-name behavior, whether the campaign must already exist, and what the agent gets back.

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?

Two short sentences, zero padding, with the core action and the key safety caveat front-loaded. The only weakness is that the terse phrasing swaps "content plan" and "assets" for the tool's own draft vocabulary, which costs a little clarity rather than words.

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

Completeness2/5

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

This is a six-parameter creation tool with no output schema and only 17 percent schema description coverage, so the description carries most of the burden. It says nothing about what a draft contains, what is returned, how the campaign reference is validated, or how the optional audience/platform fields shape the plan, which leaves the definition substantially incomplete.

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 17 percent, with only strategy_campaign_id documented, so the description should compensate but mentions no parameters at all. It does not clarify name versus objective, the platforms enum values, project_id or target_audience, leaving five of six parameters explained only by their bare types.

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

Purpose3/5

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

The verb is clear ("Create") and the output is named ("a content plan"), but the resource wording conflicts with the tool name create_post_draft and with sibling names like create_content_item and create_planner_campaign. An agent cannot tell from the description whether this makes a draft post, a content plan, or a campaign, so it does not clearly separate itself from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Nothing is published by this tool" implicitly routes publication work to schedule_post_from_draft, which is useful negative guidance. However, no alternative is named explicitly, and there is no statement of when to prefer this over create_content_item or create_planner_campaign, nor any prerequisite about the referenced campaign.

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