Skip to main content
Glama

Submit an async bulk verification job

submit_bulk

Submit a list of email addresses as an asynchronous bulk verification job — the right tool for large lists. Returns immediately with a job_id, status, and the check_status_url / results_url to poll. Small lists may complete inline (status 'completed'); larger ones return status 'pending' — poll get_job_status until it is 'completed', then call get_job_results. Optionally register a webhook_url (public HTTPS) to be notified when the job finishes.

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

Input Schema

NameRequiredDescriptionDefault
emailsYesEmail addresses to verify in this job (deduped server-side).
webhook_urlNoOptional public HTTPS URL to POST a job.completed notification to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so safety is carried structurally. The description goes further, disclosing the async contract, that small lists may return 'completed' inline, that larger ones return 'pending', and that the webhook must be a public HTTPS URL. Remaining gaps (rate limits, batch size ceilings, dedupe effects on results) are minor.

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?

A single dense paragraph, front-loaded with purpose before the workflow and the optional parameter. Every sentence carries either a decision rule or a return-value fact; nothing is redundant.

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?

With no output schema, the description must describe what comes back, and it does: job_id, status, and the check_status_url/results_url to poll. For a 2-parameter async submission tool, an agent has everything needed to call it and follow up correctly.

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; the description adds value by framing emails as a large-list bulk payload and by elaborating webhook_url as an optional completion notification rather than a per-address callback. Server-side dedupe is already in the schema, so that part earns no extra credit.

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 ("Submit a list of email addresses as an asynchronous bulk verification job") and adds the scope differentiator "the right tool for large lists." An agent can separate it from verify_email or verify_batch without opening a schema.

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 an explicit workflow: poll get_job_status until 'completed', then call get_job_results, with a webhook_url as the notification alternative. It does not explicitly state when to prefer a synchronous sibling, but the large-list guidance covers the main decision point.

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.