Skip to main content
Glama

Plan a content campaign (without creating anything)

plan_campaign

Plan a run of content the way Autopilot does — WITHOUT creating anything — so you can go through it with the user and change it first. The plan comes from what is working right now in the brand’s niche (Instagram reels on its topic) and, lightly, from what already worked on its own account; each idea has a goal (save, share, follow or lead), a format ("treatment", with how it is built) and, when it models a niche reel, that reel. Costs 25 AI credits. After the user agrees: for each idea, plan_content (its idea, hook and key points as the topic) → generate_image → create_post as a DRAFT on its suggested date; for a reel, get_reel_playbook with that idea. Or, if they just want it done, run_autopilot. For a single post or carousel, plan_content is enough. SPENDS AI CREDITS ONLY WITH confirm: true. Call it first without confirm: nothing runs and nothing is charged, you get the quote (what it will do and the credits). Tell the user, in your own words, exactly that — including the options you chose, so they can change them — and wait for a clear yes before calling again with the same arguments and confirm: true. One yes covers the plan they approved (e.g. every line of an approved voice-over with the chosen voice); anything new or different needs a new yes.

Input Schema

NameRequiredDescriptionDefault
whenNoWhen the pieces go: today, tomorrow, this_week, next_week, this_month or next_month. Default today.
countNoHow many ideas (1-20). Each one becomes a piece per account. For a week, 3-5 is typical.
topicNoOptional brief: a launch, a theme, a date. Leave it out to let the plan come from what is working in the brand’s niche and on its own account — usually the better choice.
confirmNotrue ONLY after the user said yes to the quote (what it does and the credits). Without it nothing runs and nothing is charged.
formatsNoAllowed formats. Default: whatever the accounts’ networks support.
accountIdsYesAccount ids from list_accounts (the ones to plan for).
workspaceIdNoWorkspace to work on (an id from list_workspaces). Not needed when this connection is tied to one workspace, or when you pass an account: the account's workspace is used.
idempotencyKeyNoOptional. A unique id for this action (16-128 chars: letters, digits, _ : . -). If you are unsure whether a call went through (timeout, network error), repeat it with the SAME idempotencyKey and the same arguments: you get the original result and nothing is done twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=true; the description adds substantial context beyond that: 25 AI credit cost, the confirm:true gating that guarantees nothing runs or is charged on the first call, the source of the plan (niche plus own account), and what a single approval covers. That is well above the annotation bar, but the dense prose buries these traits rather than surfacing them as distinct behaviors, keeping it at a solid 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and the no-charge first-call guarantee are front-loaded, which is good, but the single dense paragraph packs purpose, sourcing logic, credit cost, execution chain, and a multi-sentence approval protocol. Every element is relevant, yet the lack of structure (no bullets or line breaks for the confirm protocol and the per-idea chain) makes it harder to parse than its content warrants.

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?

With 8 parameters at 100% schema coverage and no output schema, the description supplies what structured fields cannot: the two-phase confirm protocol, the credit cost, the plan's data sources, and the downstream tool chain. Nothing essential to calling it correctly is missing, though the return shape of the plan (idea fields, suggested dates) is only loosely implied rather than described.

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 coverage is 100%, so the schema already documents every parameter, making 3 the baseline. The description reinforces the confirm workflow and adds practical guidance (3-5 ideas typical for a week, topic usually better left out), but it does not add syntax or format detail beyond the schema for the other parameters.

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 (plan) and resource (a run of content), and immediately scopes it with 'WITHOUT creating anything'. It names the sibling tools it is not — plan_content for a single post or carousel, run_autopilot if the user just wants it done — so an agent can route correctly without opening a 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?

Explicit when-to-use (review a plan with the user before committing), explicit alternatives (plan_content, run_autopilot, get_reel_playbook), and a full post-approval execution chain per idea. The when-not condition is also stated: a single post or carousel does not need this tool.

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