Skip to main content
Glama
agentisend

agentisend

List suppressed addresses

list_suppressions
Read-onlyIdempotent

View addresses this account will not send to and why each is suppressed, including bounce, complaint, or manual origin; pass an email to inspect one row.

Instructions

Purpose: see which addresses this account will not send to, and why each one is on the list. Pass an email to read that one row, including its id. NOT for: a general contact list (list_contacts). Returns: each row with its id, address, level, origin (bounce, complaint or manual), source_id, stream, and platform. platform true means the row applies to every account. Filter with origin when you only want one of those three.

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": "list_suppressions"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoRead one address instead of listing.
limitNoPage size (1-100).
cursorNonext_cursor from the previous page. Omit for the first page.
originNoOnly rows from bounce, complaint or manual.

Output Schema

NameRequiredDescriptionDefault
dataNoThis page of rows.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
has_moreNoTrue when another page follows.
next_cursorNoPass back as cursor for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful semantics beyond that: what 'suppressed' means here, what origin values signify (bounce, complaint, manual), and what platform=true implies. It does not describe pagination behavior, though the cursor param covers that.

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?

Front-loaded with a labeled Purpose, then exclusions, then returns. Every sentence carries information and the structure is scannable, though the Returns enumeration is dense and slightly longer than needed against an existing output schema.

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?

With an output schema present, return values need not be explained, yet the description usefully disambiguates the non-obvious platform field. Purpose, exclusions, the single-row mode, and filtering are all covered for a zero-required-param read tool.

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 meaning the schema doesn't: that passing email returns a single row including its id, and that origin selects among the three listed suppression causes. This exceeds the schema's terse field descriptions.

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 resource and scope: addresses this account will not send to, plus the reason each is listed. The 'NOT for' line against list_contacts makes the boundary explicit, so an agent can pick between the two 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?

Gives explicit when-to-use (see suppressed addresses and why), an explicit when-not-to-use with a named alternative (list_contacts), plus an alternative mode ('Pass an email to read that one row') and a filter condition for origin. Nothing is left to inference.

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