Skip to main content
Glama

Verifly

by email.verifly

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.

Input Schema

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

TDQS

A4.7/5.0
Behavior5/5

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

No annotations provided, so the description fully covers behavioral traits: asynchronous, immediate return with job_id/status/URLs, inline completion for small lists, polling guidance, and optional webhook. All critical details are disclosed.

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?

The description is concise with five sentences, front-loading the purpose. Every sentence adds information without redundancy or fluff.

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?

Despite no output schema, the description explains return fields (job_id, status, URLs) and the workflow. For two simple parameters, it covers all necessary context for an agent to use the tool 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%, baseline 3. The description adds value by noting deduplication for 'emails' and requiring 'public HTTPS' for webhook_url, providing context beyond the schema.

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?

The description clearly states the verb 'Submit' and the resource 'a list of email addresses as an asynchronous bulk verification job'. It specifies the tool is for large lists, distinguishing it from sibling tools like verify_email and verify_batch.

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?

The description explicitly says 'the right tool for large lists' and explains when inline vs polling is needed. It does not explicitly say when not to use it, but the context of siblings implies alternatives for smaller tasks.

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

All Verifly toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose. Overlaps like verify_batch vs submit_bulk are explicitly differentiated by synchronous vs asynchronous behavior. Extraction, cleaning, verification, and management tools are well-separated.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., register_account, verify_email, get_job_status). There is no mixing of conventions or vague verbs.

Tool Count5/5

15 tools cover the domain of email verification and account management without redundancy. Each tool fills a specific role—single verification, batch sync, bulk async, job polling, results retrieval, list cleaning, extraction, domain health, credit purchasing, and account management.

Completeness5/5

The tool set provides complete lifecycle coverage: account registration, usage tracking, credit purchase, email verification (single, batch, bulk with async), job management, list cleaning, email extraction, and domain health checks. No obvious gaps for the intended functionality.

Resources