BumbleBox

Edit a campaign draft (not sent)

update_campaign_draft

Idempotent

Changes the subject, body or recipient of a draft that is still a draft. Nothing is sent, and a draft the user already validated cannot be changed.

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": {
      "mission_id": "<mission_id>",
      "draft_id": "<draft_id>"
    },
    "name": "update_campaign_draft"
  }
}

Input Schema

Name	Required	Description
`to`	No
`body`	No
`subject`	No
`draft_id`	Yes
`mission_id`	Yes	Campaign id, as returned by list_missions.

Output Schema

Name	Required	Description	Default
`draft`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare mutation semantics, idempotency, and non-destructiveness. The description adds important behavioral constraints beyond annotations: this does not send anything, and validated drafts are immutable.

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?

Two concise sentences, with the main action and key restrictions front-loaded. Every sentence adds useful information without repetition.

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 mutation tool with annotations and an output schema, the description covers the essential safety and validation constraints. It is somewhat incomplete on required identifiers and parameter semantics, but the structured schema carries those details.

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 low at 20%, and the description adds meaning for three editable fields: subject, body, and recipient. However, it does not explain the required mission_id and draft_id identifiers or clarify partial-update behavior.

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

Purpose4/5

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

The description states a specific verb and resource: it changes subject, body, or recipient of a draft. It also clarifies the draft must still be a draft, which helps distinguish it from send/create operations, though it does not name sibling tools.

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

Usage Guidelines4/5

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

It gives clear usage context: edits apply only while the item is still a draft, nothing is sent, and already-validated drafts cannot be changed. It does not explicitly route to alternatives such as create_campaign_draft or list_campaign_drafts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BumbleBox tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.