Skip to main content
Glama
Sign In

Mailercloud

by com.mailercloud.mcp
OverviewDiscussionsAdmin

Delete Sender (preview, then confirm)

delete_sender
DestructiveIdempotent

Delete a sender. Campaigns can no longer be sent from it, and this can't be undone; needs sender_id. Shows a preview first and deletes only with confirm: true.

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": {
      "sender_id": "<sender_id>"
    },
    "name": "delete_sender"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to make the change. Leave it out first to get a preview, show it to the user, and ask them to confirm
dry_runNoShow what would be deleted without deleting
sender_idYesSender ID (from list_senders)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds real substance on top: the effect on campaigns and the explicit irreversibility ("can't be undone"). The preview-then-confirm protocol is behavioral context the agent cannot infer from the boolean flags alone. It stops short of covering permission requirements or how dry_run interacts with confirm.

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?

A single compact sentence that front-loads the action and then the consequences and the confirmation requirement. Zero redundant wording.

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 three-parameter destructive tool with full annotation coverage and no output schema, the definition covers purpose, consequence, and the confirm gate adequately. The one gap is the unaddressed relationship between dry_run and confirm, which could leave an agent unsure which preview mechanism to use.

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 description coverage is 100%, and the schema already explains confirm, dry_run, and sender_id in detail, so the baseline is 3. The description reinforces the required sender_id and the confirm gate, but adds little semantic detail the schema doesn't already supply, and never mentions dry_run.

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?

"Delete a sender" is a precise verb+resource statement, and the following clause spells out the downstream effect (campaigns can no longer send from it). It does not explicitly name sibling tools like list_senders or add_sender, but the operation is unambiguous against them.

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 description states the required call sequence: a preview is shown first and deletion happens only with confirm: true. That is clear guidance on how and when the destructive action takes effect, though it offers no alternatives or prerequisites (e.g. permissions, what happens if the sender is in use).

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

All Mailercloud toolsInspect
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