Skip to main content
Glama

Start a campaign (draft)

start_marketing_campaign

Start a marketing campaign from one strategy cell: save it as a DRAFT and have our AI write its copy for the channels chosen — search and social ad copy, directory/community/media/partnership outreach pitches, an email sequence. The cell needs a messaging brief first (materialize_strategy_cell). NOTHING is sent, posted, published or bought: the owner reviews the draft and exports the ads or sends the outreach themselves from the campaign screen. Social posts for content_series are written on the Posts tab, not here; platforms picks their networks. Counts toward the hourly AI limit.

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": {
      "site_id": "<site_id>",
      "cell_key": "<cell_key>",
      "channels": "<channels>"
    },
    "name": "start_marketing_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCampaign name; defaults to the cell's hook
site_idYesThe site, from list_sites
cell_keyYesA strategy cell: "persona_id:stage_id:pain_id" or "persona_id:stage_id:pain_id:competitor_id", ids from get_marketing_strategy
channelsYesWhich channels to write copy for
platformsNoNetworks content_series posts are for
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
idempotency_keyNoAny unique string; a retry with the same key returns the campaign already started instead of making a second one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
      +  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that nothing is sent, posted, published or bought and that the owner reviews and exports manually, plus a rate-limit constraint ("Counts toward the hourly AI limit"). The destructiveHint=false/openWorldHint=false annotations are corroborated and enriched with concrete operational consequences rather than merely restated.

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 the core action and outcome, then prerequisites, exclusions and constraints in a logical order; nearly every clause carries distinct information. Slightly dense with parentheticals but no redundant restatement of the name or title.

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 7-parameter creation tool with no output schema, the description covers what is created (a draft campaign), what is not done (no publishing or spend), the prerequisite, and the rate-limit implication. The only mild gap is that it does not say what identifier or object is returned to the caller, which the agent may need for follow-up review/export calls.

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 every parameter is already documented in structured form; the description mainly reinforces channel semantics (which copy types each channel produces) and adds the cell prerequisite, but it does not explain cell_key syntax, idempotency_key behavior, or the name default beyond what the schema says. Baseline 3 is appropriate when the schema already carries the parameter burden.

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 (start a marketing campaign from one strategy cell) and defines exactly what the tool produces: a draft with AI-written copy for the chosen channels, with an explicit enumeration of the copy categories. It also carves out scope against a sibling behavior (content_series posts belong on the Posts tab), so an agent can distinguish it from draft_campaign, materialize_strategy_cell and spawn_campaign_landing_page without opening schemas.

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 prerequisite ("The cell needs a messaging brief first (materialize_strategy_cell)"), an explicit exclusion (social posts for content_series are written on the Posts tab, not here), and a clarification of which parameter governs which side effect (platforms picks content_series networks). The when-to-use and when-not-to-use conditions are both stated with the alternative named.

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