SendPulse WhatsApp MCP

Overview Schema Source Related Servers Discussions Admin

Disable Contact

sendpulse_disable_contact

DestructiveIdempotent

Disable a SendPulse WhatsApp contact to stop bot messages. Provide the contact ID and account name to halt automated chatbot outreach.

Instructions

Disable a contact so they stop receiving bot messages.

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

Input Schema

Name	Required	Description	Default
`account`	No	Account name (only one configured: brand_a)	brand_a
`contact_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Oct 1, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is known. The description adds the observable effect of stopping bot messages, which is useful context, but it does not explain reversibility, permissions, or what state changes occur.

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 definition is a single efficient sentence that is front-loaded with the action and includes the effect without any wasted wording.

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 two-parameter tool with rich annotations and no output schema, the description covers the core action and effect. However, it omits usage distinctions from related tools and leaves the required contact_id parameter undocumented, making it only minimally complete.

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 50%, and the required contact_id parameter has no description in either the schema or the tool description. The description adds no meaning about how to identify the contact or what the account parameter defaults to, so it does not compensate for the coverage gap.

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 ('Disable') and resource ('a contact') and adds the intended effect ('stop receiving bot messages'). It is clearly distinguishable from sendpulse_enable_contact, though it does not explicitly name that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies when the effect is desired but gives no explicit context or exclusions. Critically, it does not distinguish disabling a contact from sibling tools like sendpulse_pause_contact_automation or sendpulse_resume_contact_automation, leaving the agent to infer the difference.

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