Unitpost

Email campaigns · reschedule

email_campaigns_reschedule

Destructive

Move a SCHEDULED campaign to a new future send time (scheduled_at: ISO 8601 with Z or an offset like -07:00; returned in UTC). A draft is scheduled with email_campaigns_send instead.

Scope: campaigns:send.

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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "email_campaigns_reschedule"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Campaign id (`cmp_…`).
`body`	Yes	`{ scheduled_at }` — new ISO 8601 send time (SCHEDULED campaigns only).

Output Schema

Name	Required	Description	Default
`data`	No
`hint`	No
`status`	No
`warning`	No
`request_id`	No
`retry_after_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Adds context beyond the annotations: the status restriction (SCHEDULED only), the requirement that the new time be in the future, the `campaigns:send` auth scope, and UTC normalization of the returned value. It does not address the destructiveHint=true / idempotentHint=false profile — nothing says whether the prior schedule is discarded or what happens on retry — which is the main remaining gap.

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?

Three short, front-loaded statements — action, draft-scheduling exception, permission scope — with no filler or repetition of the title.

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 two-parameter mutation with full schema coverage, annotations, and an output schema, the description covers selection, preconditions, and time format adequately. It stops short of describing failure behavior for non-scheduled campaigns or the effect on an existing schedule, which keeps it from being fully complete.

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 already 100%, so the baseline is 3, but the description adds real meaning: accepted ISO 8601 forms (`Z` or an offset like `-07:00`) and that the value comes back in UTC. It also implicitly clarifies that the nested `body` object wraps a single `scheduled_at` field.

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 ('Move a SCHEDULED campaign') plus the operand ('to a new future send time'), which lets an agent distinguish it from email_campaigns_update, email_campaigns_send, and email_campaigns_pause without opening any 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?

Gives an explicit precondition (only SCHEDULED campaigns) and names the correct alternative for the excluded case: 'A draft is scheduled with email_campaigns_send instead.' The required permission scope is also stated, so the agent knows when this call will be rejected.

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

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