Sendblox

Generate Campaign Copy

generate_campaign_copy

Idempotent

APP: Asks Sendblox to draft outbound email campaign copy. Local/default generation is fixture-only and labelled as such. Never returns prompts or model reasoning. Does not send and does not publish a web page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_campaign_copy"
  }
}

Input Schema

Name	Required	Description	Default
`tone`	No
`contact`	No
`language`	No
`objective`	No
`campaignId`	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

B3.3/5.0

Behavior4/5

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

Beyond the annotations, the description adds meaningful behavioral details: local/default generation is fixture-only and labelled as such, prompts and model reasoning are never returned, and the tool does not send email or publish a web page. This is strong context for a non-read-only but non-destructive, idempotent operation.

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?

The description is short, front-loaded, and every sentence adds useful information. It avoids repetition and communicates the key scope and side-effect boundaries efficiently.

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?

The description covers purpose and important side-effect behavior, and an output schema exists so return values need not be explained. However, with 10 parameters, a nested contact object, and 0% schema description coverage, the definition is not complete enough for an agent to invoke the tool correctly without guessing parameter semantics.

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

Parameters1/5

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

There are 10 parameters with 0% schema description coverage, yet the description provides no information about any parameter, including tone, contact, language, objective, campaignId, idempotencyKey, or external identifiers. The agent cannot infer parameter meaning or expected format from either schema or description.

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: draft outbound email campaign copy via Sendblox. It also distinguishes the tool from sending and publishing actions, though it does not name or compare against sibling tools such as preview_message or create_campaign.

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?

It implies usage by saying the tool drafts campaign copy and clarifies that it does not send or publish a web page. However, it gives no explicit routing guidance versus siblings like create_campaign or preview_message, and no prerequisites or when-not-to-use conditions beyond the negative side-effect statements.

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?