SendPulse WhatsApp MCP

Overview Schema Source Related Servers Discussions Admin

Pause Contact Automation

sendpulse_pause_contact_automation

Pause all automated WhatsApp flows for a contact for a set number of minutes, such as while a human agent handles the chat.

Instructions

Pause all automated flows for a contact for a specified number of minutes (e.g. while a human agent is handling the chat).

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": {
      "contact_id": "<contact_id>",
      "minutes": "<minutes>"
    },
    "name": "sendpulse_pause_contact_automation"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No	Account name (only one configured: brand_a)	brand_a
`minutes`	Yes	Minutes to pause automation
`contact_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Oct 1, 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=false, and openWorldHint=true, so the agent knows this is a non-destructive, non-idempotent mutation. The description adds that the pause has a bounded duration and covers *all* flows, but says nothing about what happens after the timer expires, whether in-flight messages are halted, or whether re-pausing extends the window.

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?

One tightly written sentence; the core action and its temporal scope are front-loaded before the illustrative example. Nothing is wasted.

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?

For a simple 3-param mutation with annotations covering the safety profile and no output schema, the definition is adequate but leaves gaps: the undocumented contact_id, post-expiry behavior, and interaction with the resume sibling are all unaddressed.

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

Parameters3/5

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

Schema coverage is 67%: 'minutes' and 'account' are documented in-schema, but 'contact_id' is a bare string with no description in either place. The description restates the time-bound meaning of 'minutes' but adds no format, identifier-shape, or default-value detail beyond the schema.

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?

States a specific verb (pause), resource (automated flows), and scope (all flows for one contact, time-bounded). It's clearly distinguishable from sendpulse_disable_contact (permanent disable) and sendpulse_resume_contact_automation. It does not name the resume sibling explicitly, so it falls just short of 5.

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 parenthetical '(e.g. while a human agent is handling the chat)' supplies a concrete when-to-use scenario, which is more than most siblings offer. It stops short of naming the resume counterpart or stating when *not* to pause (e.g. already-paused contacts).

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