CDP MCP Server

cdp_delete_mailer_account

Remove a mailer account from the CDP platform by soft-deleting it, which retains data for recovery while disabling active use.

Instructions

Soft-delete a mailer account (DELETE /v2/{tenantId}/mailer/accounts/{id}).

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

Input Schema

Name	Required	Description	Default
`id`	Yes
`tenant_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 21, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the 'soft-delete' behavior (implying reversible deletion rather than permanent removal), which is valuable context beyond just 'delete'. However, it lacks details on permissions needed, side effects, rate limits, or what the soft-delete entails operationally.

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 a single, efficient sentence that front-loads the key action ('soft-delete a mailer account') without unnecessary words. The HTTP method inclusion is concise and adds technical context without verbosity.

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 deletion tool with no annotations, 0% schema coverage, but an output schema (which handles return values), the description is minimally adequate. It covers the core action and hints at reversibility ('soft-delete'), but lacks parameter explanations, usage context, and full behavioral details needed for safe invocation.

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 0%, so the schema provides no parameter descriptions. The description mentions no parameters at all, failing to compensate for the coverage gap. It doesn't explain what 'id' or 'tenant_id' represent or their significance for the operation.

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 clearly states the action ('soft-delete') and resource ('a mailer account'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from other delete operations in the sibling list (like cdp_delete_mailer_subuser or general delete tools), which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. Given the sibling tools include cdp_restore_mailer_account, there's an implied alternative for undoing deletions, but this isn't stated in the description itself.

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

Deploy Server