Skip to main content
Glama
Sign In

Emailchaser

by com.emailchaser
OverviewDiscussionsAdmin

List blocklist entries

list_blocklist_entries
Read-only

Returns the suppression entries (blocked domains and email addresses) that apply to this workspace, newest first. Blocked entries are never emailed by any campaign. By default that spans both lists: this workspace's own entries and the account-wide ones inherited from the main workspace. Each entry reports which list it came from.

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_blocklist_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (default 100, max 1,000)
scopeNoWhich list to return: "workspace" for this workspace's own entries, "global" for the account-wide list, "all" for both (default)
offsetNoNumber of entries to skip (default 0)
searchNoCase-insensitive substring match on the domain or address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already mark this readOnly, non-destructive, and closed-world, and the description adds meaningful behavior beyond that: results are newest first, blocked entries are never emailed by any campaign, and each row reports which list it originated from. It stops short of describing pagination totals or result-shape details, but the uncovered ground is modest.

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?

Four short sentences, front-loaded with the return contents, then scope, then row provenance. The 'by default that spans both lists' sentence partly restates the scope parameter's default, which is slightly redundant, but every other sentence carries information an agent would use.

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 read-only listing tool with no output schema and a fully documented input schema, this gives the agent enough: what is returned, ordering, default scope, and the source-list field per row. It leaves out pagination behavior and a sense of result volume, which are minor for a paged list tool.

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%, so all four parameters (limit, scope, offset, search) are already documented, and the baseline is 3. The description reinforces the default dual-list scope and mentions ordering, which is relevant to how offset/limit paging behaves, but it adds no syntax or format detail beyond the schema.

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?

The description opens with a precise verb+resource: it 'returns the suppression entries (blocked domains and email addresses)' and defines their scope as workspace-applicable, newest first. That wording separates it cleanly from the mutating and single-entry siblings (add/remove/update/get_blocklist_entry) without needing to name 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?

It gives clear context for calling it: the result set spans the workspace's own list plus the account-wide inherited list by default, and the scope enum is spelled out in the schema for narrowing. What's missing is an explicit exclusion telling the agent when to reach for get_blocklist_entry or a different list tool instead.

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

All Emailchaser 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