Skip to main content
Glama

Email verify bulk

email_verify_bulk
Read-onlyIdempotent

Bulk email validate. Bulk email list verifier (up to 100 addresses): syntax, live DNS MX records, disposable-domain and role-account detection. $0.009 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "emails": "<emails>"
    },
    "name": "email_verify_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailsYescomma-separated email addresses, up to 100
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds behavior annotations cannot express: per-call cost ($0.009), the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and that the purchase completes inside the call when `payment` is supplied. The one gap is that nothing is said about the shape of the verification results, which matters since there is no output schema.

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 and dense: capability, limits, checks, price, and payment mechanics in three short sentences with no filler. The opening 'Bulk email validate. Bulk email list verifier' is mildly redundant, restating the same capability twice.

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

Completeness3/5

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

For a paid, two-step tool with no output schema, the description covers the invocation protocol and cost well but leaves the return contract undefined — an agent cannot tell whether results are per-address, aggregated, or how failures for individual addresses are reported. Complexity is moderate (bulk + payment), so this is a meaningful omission rather than a fatal one.

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 both parameters are already documented in the input schema, which sets the baseline at 3. The description adds real meaning about `payment` by framing it as the second half of a two-step flow (get terms, then sign and resubmit), but it adds nothing about the `emails` format beyond what the schema already says.

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?

States a specific verb and resource ('Bulk email list verifier ... up to 100 addresses') and enumerates the actual checks performed: syntax, live DNS MX records, disposable-domain and role-account detection. This is far more specific than a name restatement. It does not differentiate from the closest sibling (email_security), which is the only thing holding it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives useful procedural guidance for the payment handshake ('Call once without `payment` for the terms ... call again with `payment`'), which is genuinely actionable. However it never says when to choose this over the related email_security tool, nor does it state exclusions such as list size limits beyond 100 or what to do on partial failure.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources