Skip to main content
Glama

Update draft

campaign_update
Idempotent

Edits a campaign while it is still a draft: any of name, template, subject, preheader, blocks, audience or the survey question. Fields you leave out stay as they are; blocks you pass replace the whole blocks object; survey null removes the question. Uses no quota and sends nothing. Refused with campaign_locked once the campaign is scheduled or sent. Run campaign_preview again after editing. 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": {
      "id": "<id>"
    },
    "name": "campaign_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCampaign id (a UUID), as returned by campaign_draft or campaigns_list.
nameNoNew internal name.
blocksNoContent 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.
surveyNoSet the survey question, or null to remove it.
subjectNoNew subject line.
audienceNoWho gets it: {"tags": ["vip"]} for tagged contacts, or {"all": true} for every subscribed contact, or {"signup_form_id": "<UUID>"} for a waitlist.
preheaderNoNew preview text.
template_idNoNew template 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?

Goes well beyond the annotations by disclosing patch semantics (omitted fields persist), that blocks replace the entire blocks object, that survey null removes the question, that no quota is consumed, that nothing is sent, and the required API key scope. The annotations only declare readOnly=false, idempotent=true, destructive=false; the description supplies the operational detail that lets an agent call it safely.

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

Conciseness5/5

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

Six compact sentences, front-loaded with purpose and scope, then merge semantics, then side effects, then failure mode, then next step. No filler, no restatement of the title, and each sentence carries a distinct decision-relevant fact.

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 an 8-parameter nested mutation tool with no output schema, the description covers side effects, scope gating, merge semantics, and follow-up. The only small gap is that it does not name campaign_draft as the creation alternative or describe what the response returns, but neither is critical given idempotentHint and the full schema.

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 is 3, but the description adds meaning not in the schema: fields left out stay unchanged, blocks is a wholesale replace rather than a merge, and survey null is the removal signal. That is genuine semantic value for the three ambiguous 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?

Opens with a specific verb and resource ("Edits a campaign") plus a hard scope constraint ("while it is still a draft") and enumerates exactly which fields are editable, so the agent can distinguish it from campaign_draft, campaign_schedule, and campaign_preview without opening any 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?

States the exclusion condition explicitly ("Refused with campaign_locked once the campaign is scheduled or sent") and prescribes the follow-up step ("Run campaign_preview again after editing"), giving both when-not and what-to-do-instead. It also clarifies this never sends anything, which separates it from campaign_send_test and campaign_schedule.

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