Skip to main content
Glama
agentisend

agentisend

Allow sending to an address again

remove_suppression
DestructiveIdempotent

Re-enable email delivery to a suppressed address after fixing the underlying block, such as a full mailbox or mistyped address, by supplying its ID or email address.

Instructions

Purpose: let mail reach an address again, once you know the reason it was blocked is gone — a mailbox that was full, an address that was mistyped. Pass the id or the address. NOT for: an address that unsubscribed or reported a message as spam. Those are refused with human_action_required: somebody said no, and only they can change that. A platform row cannot be removed from this account. Returns: the id and confirmation it is gone. Removing a hard bounce you have not actually fixed damages every send that follows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "remove_suppression"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe address, when you do not have the id.
suppression_idNoThe id from list_suppressions.
idempotency_keyNoYour own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect.

Output Schema

NameRequiredDescriptionDefault
idNoIdentifier.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
removedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint and idempotentHint, but the description adds the refusal semantics for consent-based suppressions, the warning that removing an unfixed hard bounce damages subsequent sends, and the confirmation returned. That is richer behavioral context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structured into Purpose / NOT for / Returns and front-loaded, with each clause carrying information. The explicit section labels add slight boilerplate overhead, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, idempotent mutation with an output schema and fully documented parameters, the description covers the decisions an agent must make: when it is safe to call, when it will be refused, and the consequence of calling it wrongly.

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 100%, so the baseline is 3, but the description adds real meaning by stating 'Pass the id or the address' — clarifying that these two optional parameters are alternatives, which the schema does not express. It adds no format detail beyond that.

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 — re-allowing mail to an address by removing its suppression — plus the intended scope (bounce/mistyped addresses). An agent can distinguish this from add_suppression and list_suppressions without opening either 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?

Explicit 'NOT for' clause names the two excluded cases (unsubscribed, spam complaint) and explains the refusal outcome (human_action_required), plus the platform-row restriction. It also names the condition for using the id (from list_suppressions).

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