Skip to main content
Glama
Sign In

Emailchaser

by com.emailchaser
OverviewDiscussionsAdmin

Add blocklist entries

add_blocklist_entries
Idempotent

Adds up to 1,000 suppression entries in one call so no campaign ever emails them. Each value is either a full email address (contains @) or a bare domain; the type is inferred per value. Existing entries and invalid values are skipped, so the call is safe to retry and suited to carrying over a suppression list from another sending platform. Scope defaults to "workspace"; "global" blocks across every workspace on the account and only works from the main workspace.

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": {
      "values": "<values>"
    },
    "name": "add_blocklist_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNo"workspace" (default) blocks for this workspace only; "global" blocks for every workspace on the account
valuesYesEmail addresses and/or domains to block, e.g. ["competitor.com", "jane@acme.com"] (1 to 1,000 per request)

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.6/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare non-read-only, idempotent, non-destructive, closed-world) by disclosing per-value type inference, silent skipping of existing and invalid values, and — most importantly — that 'global' scope only works from the main workspace, an authorization constraint an agent cannot infer anywhere else.

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?

Three sentences, front-loaded with capacity and purpose, then value semantics, then scope/permission behavior. Every sentence carries a distinct, decision-relevant fact with no restatement of the schema.

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 two-parameter mutation with no output schema, the description covers effect, capacity, skipping semantics, retry safety, and scope permissions — everything needed to call it correctly. It does not say what the response reports about skipped entries, which is the one remaining gap for a bulk operation.

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; the description still adds meaning by explaining that each value's type (email vs. bare domain) is inferred per item rather than declared, and by restating the default and constraint on 'scope'. It leaves the accepted domain syntax rules unstated, so not a 5.

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 ('Adds ... suppression entries') plus a hard capacity limit ('up to 1,000 in one call') and the effect ('so no campaign ever emails them'). The verb 'adds' cleanly distinguishes it from the list_/remove_/get_ blocklist siblings 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?

Gives a concrete use case ('carrying over a suppression list from another sending platform') and a retry rationale ('safe to retry'), which tells the agent when this call is appropriate. It stops short of explicit when-not-to-use guidance or naming an alternative for single-entry additions, so it is clear context rather than full routing.

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