Skip to main content
Glama

Email Verifier & Domain Validator

email_domain_validator

Validate email addresses and domains by checking syntax, common typos, MX/A DNS, disposable providers, role accounts, and SPF/DMARC records. Clean mailing lists from email lists or CSV URLs.

Instructions

Validate email addresses and domains: syntax checks, typo suggestions (for example gmial.com), MX and A DNS lookup, disposable and temporary email detection, free-provider flags, role accounts (info@, support@), SPF and DMARC records. Accepts a list of emails, domains, or a CSV URL. No SMTP mailbox probe. Use this to verify emails, clean mailing lists and validate domains. Van Born Labs. $0.50 per 1,000 results, billed to your Apify account.

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

Input Schema

NameRequiredDescriptionDefault
csvUrlNoHTTP(S) URL of a CSV file with an email and/or domain column. Combined with the lists above, then deduped.
emailsNoEmail addresses to validate (one per line). Duplicates are skipped.
domainsNoDomain names to check for A, MX, SPF and DMARC records (no mailbox).
maxItemsNoHard cap on validated (and charged) unique emails and domains in this run. Defaults to 10 in this MCP server to keep runs cheap.
suggestTyposNoSuggest a corrected domain for common typos such as gmial.com or gmail.con.
csvEmailColumnNoColumn name for emails. Leave empty to auto-detect (email, e-mail, mail, …).
maxConcurrencyNoParallel DNS-over-HTTPS lookups.
csvDomainColumnNoColumn name for domains. Leave empty to auto-detect (domain, website, url, …).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing cost ($0.50 per 1,000 results billed to the Apify account), the default MCP cap of 10 items chosen to keep runs cheap, and the deliberate absence of an SMTP probe. These are exactly the operational facts an agent needs before invoking a paid, open-world tool; nothing here contradicts 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph that front-loads the capability list, then the input shapes, then exclusions, then pricing. Every sentence carries information; the feature enumeration is slightly list-heavy but each item is a distinct check rather than filler.

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 an 8-parameter, no-output-schema tool this covers purpose, inputs, exclusions, cost, and the run cap. The main remaining gap is that the shape of the returned results is only implied ('results' used as the billing unit), which matters since there is no output schema to fall back on.

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 every parameter is already documented in structured data, and the description only restates the input shapes (list of emails, domains, or CSV URL). It adds no extra syntax, precedence, or format guidance beyond what the schema provides, so the baseline 3 applies.

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 (validate) and resources (email addresses and domains), then enumerates the concrete checks performed: syntax, typo suggestions, MX/A DNS, disposable detection, role accounts, SPF/DMARC. The one-line 'No SMTP mailbox probe' further delimits what the tool does not do, so an agent can distinguish its scope from a generic mail-checker.

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?

Explicitly says 'Use this to verify emails, clean mailing lists and validate domains,' which names the intended tasks. It also sets a negative boundary ('No SMTP mailbox probe'). It does not name alternatives or when-not-to-use cases, but the sibling list contains no overlapping validator tools, so that omission is low-cost.

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