Sendblox

Create Campaign

create_campaign

Idempotent

APP: Creates an outbound email campaign in DRAFT / PREPARE_AND_HOLD. Never launches or sends, and does not create a campaign web page.

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

Input Schema

Name	Required	Description	Default
`mode`	No
`name`	Yes
`senderId`	No
`objective`	No
`audienceId`	No
`reviewMode`	No
`sequenceId`	No
`idempotencyKey`	No
`externalProjectId`	No
`externalCampaignId`	No
`externalObjectiveId`	No
`externalCorrelationId`	No

Output Schema

Name	Required	Description	Default
`jobId`	No
`result`	Yes
`status`	Yes
`summary`	No
`blockers`	Yes
`warnings`	Yes
`readiness`	No
`requestId`	Yes
`retryable`	No
`nextPossibleActions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the safety profile is covered; the description adds real value by disclosing the non-sending, no-web-page boundaries. It omits anything about idempotencyKey semantics despite the idempotent annotation, and its mention of only DRAFT/PREPARE_AND_HOLD omits the PREPARE_AND_REVIEW mode present in the enum.

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 short sentences, front-loaded with the action and the resulting state, then the negative boundaries. Every clause earns its place with no filler.

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

Completeness2/5

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

An output schema exists so return values need not be explained, but for a 12-parameter creation tool with zero schema descriptions the definition does almost nothing to explain required relationships or key identifiers. It also leaves the three-value mode enum and idempotency behavior undocumented.

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?

Schema description coverage is 0% across 12 parameters, and the description only alludes to mode states without defining mode, senderId, audienceId, sequenceId, or idempotencyKey. It also under-reports the mode enum by naming two of the three accepted values.

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 an outbound email campaign) plus the resulting states (DRAFT / PREPARE_AND_HOLD). It also draws boundaries against siblings implicitly: launch_campaign exists, and the description explicitly says this never launches or sends, and it does not create a campaign web page.

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?

The 'never launches or sends' clause tells an agent this is the setup step and that launch_campaign is the follow-up, which is strong implied routing. However, no sibling is named outright and there is no guidance on which mode value to pick or when to prefer this over create_sequence.

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

All Sendblox 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.

Resources

Need Help?