Emailchaser

Remove blocklist entries

remove_blocklist_entries

DestructiveIdempotent

Unblocks up to 1,000 domains or email addresses in one call, so campaigns can email them again. Pass values (domains or addresses, matched case-insensitively) and/or ids (blocklist entry IDs); a value that is not blocked is counted as skipped rather than failing the call. Scope defaults to "workspace" and never touches the account-wide list unless asked; removing an account-wide entry only works from the main workspace.

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

Input Schema

Name	Required	Description
`ids`	No	Blocklist entry IDs to remove (from list_blocklist_entries). Provide values, ids or both
`scope`	No	Which list to remove from: "workspace" (default), "global", or "all"
`values`	No	Email addresses and/or domains to unblock, e.g. ["competitor.com", "jane@acme.com"] (1 to 1,000 per request)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedSep 12, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations (destructive, idempotent, non-read-only), the description discloses partial-failure tolerance ("a value that is not blocked is counted as skipped rather than failing the call") and case-insensitive matching. It also explains the blast radius of the default scope and a deployment constraint: removing an account-wide entry only works from the main workspace.

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 tightly packed sentences with no filler: purpose and batch limit first, then how to call it and skip semantics, then scope behavior. Each clause carries operational information the agent needs.

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 destructive mutation with no output schema, the definition covers purpose, accepted inputs, failure tolerance, scope defaults, and a workspace restriction. The remaining gap is what the response contains (counts of removed vs. skipped), which is a minor omission given the skip behavior is already described.

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 baseline is 3, but the description still adds meaning: values are matched case-insensitively, unblocked values degrade to "skipped" rather than erroring, and scope defaults to workspace without touching the account-wide list. The "all" enum value is left to the schema to explain.

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?

"Unblocks up to 1,000 domains or email addresses in one call" gives a specific verb, resource, and batch scale, which implicitly separates it from the singular remove_blocklist_entry sibling. It never names that sibling outright, so the differentiation depends on the agent noticing the 1,000-item framing.

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 states the business purpose (so campaigns can email them again) and explains that either values or ids, or both, may be supplied. Constraint guidance is present for scope ("defaults to workspace and never touches the account-wide list unless asked") and for the main-workspace restriction, but there is no explicit instruction on when to prefer remove_blocklist_entry for a single entry.

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

All Emailchaser tools Inspect

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

Need Help?