Skip to main content
Glama

Start a batch verification

create_verify_batch

Start verifying a list of up to 50,000 email addresses in the background. Returns a batch_id straight away with status queued; poll get_batch_status until it is completed, then read results with get_batch_items. Reserves 1 credit per address up front and refunds cache hits, duplicates, malformed addresses and results we can't resolve when the batch finishes. Use this for lists; for a single address use decide_send.

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

Input Schema

NameRequiredDescriptionDefault
emailsYesThe email addresses to verify, 1 to 50,000. Duplicates are verified once.
strictnessNoHow cautious the recommended action is. default: catch-all domains get review. aggressive: catch-all domains get send_with_caution. strict: as default, and role addresses such as info@ or sales@ also get review. Defaults to default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / webhook_url
      Removed value: -{
      -  "description": "Optional HTTPS URL that receives a POST when the batch finishes. The body is signed with HMAC-SHA256 in the x-inboxpolicy-signature header, using the webhook_secret this call returns.",
      -  "type": "string"
      -}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true); the description adds the async contract, the immediate queued return, the polling requirement, and the credit reservation/refund policy. Those are exactly the operational traits annotations cannot express, and none of them contradict the supplied hints.

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?

Four dense sentences with zero filler, ordered by importance: what it does, how to retrieve results, what it costs, and when to pick the alternative. The action and the workflow lead; the cost caveat follows.

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?

Even without an output schema, the description explains what comes back (a batch_id with status queued) and how the result is eventually obtained, so no return-value gap remains. For a two-parameter async job tool with full schema coverage, nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the schema already documents both emails and strictness, including the enum meanings. The description adds only marginal parameter-adjacent meaning (duplicates are refunded when the batch finishes), which reinforces the schema's "Duplicates are verified once" but does not go beyond it.

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?

Opens with a specific verb and resource plus scope: "Start verifying a list of up to 50,000 email addresses in the background." It immediately names the sibling it is not (decide_send for single addresses), so an agent can route without opening another 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 an explicit when-to-use rule ("Use this for lists") and the condition that selects the alternative ("for a single address use decide_send"). It also states the required follow-up sequence: poll get_batch_status until completed, then read results with get_batch_items.

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