BumbleBox

List the drafts of a campaign

list_campaign_drafts

Read-only

The drafts of one campaign that wait for the user to validate them in BumbleBox (recipient, subject, plain-text body, sender), newest first, with the true totals.

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>"
    },
    "name": "list_campaign_drafts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`mission_id`	Yes	Campaign id, as returned by list_missions.

Output Schema

Name	Required	Description	Default
`counts`	Yes
`drafts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, non-open-world operation. The description adds useful behavior beyond that: results are newest first, pending validation is the implicit filter, and the totals are 'true' totals. It still does not explain pagination behavior or how limit affects returned totals.

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?

It is a single tightly packed sentence with no filler. Scope, status, ordering, returned fields, and totals are all front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover safety, so the description needn't explain return internals. Still, it omits limit semantics and any guidance on when this tool should be chosen over related listing tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The mission_id parameter is documented in the schema, and the description's phrase 'one campaign' reinforces it. But the limit parameter is undocumented in both the schema and the description, and with only 50% schema description coverage the description should compensate for that gap.

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 clearly identifies the resource: drafts belonging to one campaign that are awaiting validation. It also lists returned fields and ordering, but it does not explicitly differentiate itself from nearby sibling tools such as list_replies_to_validate or update_campaign_draft.

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

Usage Guidelines3/5

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

The phrase 'wait for the user to validate them in BumbleBox' implies the use case: retrieving pending campaign drafts for review. However, it gives no explicit when-to-use guidance, no exclusions, and no comparison to alternative listing tools.

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.