Skip to main content
Glama

Draft campaign

campaign_draft

Creates a campaign as a DRAFT. Nothing is sent and no quota is used. Before calling: read brand_get for the voice, pick a template from templates_list, and pick the audience from segments_list. You fill the content blocks; Hollerpost renders the email with the brand header, footer and unsubscribe link. Optionally ask one survey question (survey) that readers answer with one click. Returns the id, audience_count and a preview_url to share with the person. Next step: campaign_preview, then campaign_send_test. Retail promo in one call (template promo): {"info_bar": {"text": "Free shipping over $99", "url": "https://shop.example/shipping"}, "image_url": "https://images.hollerpost.com/...", "image_alt": "...", "image_link": "https://shop.example/sale", "heading": "Up to 30% off", "body_md": "...", "cta_text": "Shop the sale", "cta_url": "https://shop.example/sale", "cta_repeat": "bottom", "layout": "grid-2", "sections": [{"heading": "Maple cue", "price": "$129", "image_url": "https://images.hollerpost.com/...", "image_alt": "Maple cue", "cta_text": "Shop now", "cta_url": "https://shop.example/p/1"}], "fine_print": "Ends Sunday. Not valid with other offers.", "theme": {"button_style": "outline", "button_shape": "pill"}}. The footer link buttons, Follow us icons and disclaimer come from the brand (brand_set_footer), not the blocks. Every send also gets a View in browser link, the mailing address and an unsubscribe link automatically. Requires API key scope: draft.

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>",
      "template_id": "<template_id>",
      "subject": "<subject>",
      "blocks": "<blocks>",
      "audience": "<audience>"
    },
    "name": "campaign_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesInternal campaign name (recipients do not see it).
blocksYesContent blocks for the template. Check templates_list for the blocks_schema of the template you pick. Never send raw HTML: Hollerpost renders the blocks with the brand header, footer, unsubscribe link and address. The plain template takes no images.
surveyNoAsk one survey question in the email; readers answer with one click. The survey must be open (survey_update with status "open") before the campaign can be test-sent or scheduled.
subjectYesEmail subject line.
audienceYesWho gets it: {"tags": ["vip"]} for tagged contacts, or {"all": true} for every subscribed contact, or {"signup_form_id": "<UUID>"} for a waitlist.
preheaderNoPreview text shown after the subject in most inboxes.
template_idYesTemplate id from templates_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover readOnly/destructive/idempotent hints; the description goes well beyond them by disclosing that nothing is sent, no quota is consumed, rendering is server-side (header, footer, unsubscribe, view-in-browser, mailing address added automatically), and that the API key needs the "draft" scope. It also names the return fields (id, audience_count, preview_url) with no output schema present.

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 single most important fact (draft, nothing sent) and organized with clear "Before calling:" and "Next step:" markers. It loses a point for length and mild redundancy — the automatic unsubscribe/mailing-address rendering is stated twice, and the long inline JSON example overlaps substantially with the schema.

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 7-parameter tool with deeply nested blocks, a survey object, and three audience variants, the description covers prerequisites, rendering behavior, auth scope, return values, and the follow-up workflow. With no output schema, it still names what comes back, so nothing an agent needs to call or chain this tool 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 baseline would be 3; the description earns more by adding a complete worked retail-promo payload, clarifying that footer buttons/Follow icons/disclaimer come from brand_set_footer rather than blocks, and warning that the plain template takes no images. These are behavioral facts about parameter usage not encoded in the schema itself.

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 ("Creates a campaign as a DRAFT") and immediately bounds the effect ("Nothing is sent and no quota is used"), which cleanly separates it from campaign_send_test and campaign_schedule. An agent can identify the tool and its non-destructive nature without opening the 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 prerequisite chain is given: "read brand_get for the voice, pick a template from templates_list, and pick the audience from segments_list," plus an explicit next-step path ("campaign_preview, then campaign_send_test"). It also states a hard constraint (survey must be open before test-send or schedule), which is exactly the kind of routing/exclusion guidance that prevents misuse.

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