Sendocado

Update campaign

update_campaign

Idempotent

Replace a campaign's name, time zone, send window, reply handling and audience, all at once: every field is required and none has a default. Read the campaign with get_campaign first and send back what should stay; filter_groups [] means every contact. On a live campaign the new audience applies at once: new matches are enrolled and people who stop matching leave. The status never changes here (set_campaign_status), and steps are edited with the step tools.

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": {
      "campaign_id": "<campaign_id>",
      "name": "<name>",
      "timezone": "<timezone>",
      "send_window": "<send_window>",
      "is_stopped_on_reply": "<is_stopped_on_reply>",
      "filter_groups": "<filter_groups>"
    },
    "name": "update_campaign"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`timezone`	Yes	IANA time zone.
`campaign_id`	Yes
`send_window`	Yes	When emails may go out, in the contact's time zone (else the campaign's). Null sends at any hour.
`filter_groups`	Yes	A contact matches when it passes every filter of at least one group. An empty list means every contact in the project.
`is_stopped_on_reply`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare the mutation-safe profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower, yet the description still adds real behavioral facts: this is a full replacement where every field is required and nothing is defaulted, and on a live campaign the audience is re-evaluated immediately with enrolments and removals following. That last point is a side effect not visible in the schema, which an agent could otherwise trigger unknowingly.

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?

Four dense sentences, front-loaded with the replace-all semantics before the workflow advice, then side effects, then exclusions. Every clause carries information an agent needs; nothing is restated from the schema or annotations.

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 six-required-parameter mutation with no output schema and a non-trivial nested audience structure, the description covers replacement semantics, the read-first workflow, the empty-filter meaning, live-campaign side effects, and the boundaries against status and step tools. What is missing is modest: no mention of error or validation behavior, and no guidance on what the response returns (acceptable, since there is no output schema but it is also not promised).

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 only 50%, so the description carries extra burden; it correctly emphasizes that all six parameters are required with no defaults and pins down filter_groups [] as "every contact". It does not describe the nested filter shapes (tag/attribute/recency/campaign predicates), though those are documented in the schema itself, so it compensates for the key gaps without exhausting them.

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?

"Replace a campaign's name, time zone, send window, reply handling and audience, all at once" names a specific verb (replace), the resource (campaign) and the exact fields involved. It also explicitly rules out two adjacent operations by name (set_campaign_status, the step tools), so an agent can distinguish it from update_campaign_step or set_campaign_status without opening either 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?

The description prescribes the read-modify-write workflow ("Read the campaign with get_campaign first and send back what should stay"), which is essential for a full-replacement update and is not inferable from the schema. It also names the alternatives for the excluded concerns (status via set_campaign_status, steps via the step tools) and clarifies the empty-audience edge case.

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

All Sendocado 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?