Skip to main content
Glama

Check domain & email health (SPF, DKIM, DMARC, TLS, DNS)

check_domain_email_health
Read-only

Check a domain's email authentication and deliverability, DNS hygiene, and TLS certificate expiry to flag spoofing risks and Gmail/Yahoo bulk-sender gaps with exact DNS records to add.

Instructions

Checks a domain's email authentication and deliverability setup (MX, SPF, DKIM, DMARC policy, BIMI, MTA-STS/TLS-RPT), DNS hygiene (DNSSEC, CAA, nameservers) and HTTPS/TLS certificate expiry. Flags spoofing risk and Gmail/Yahoo bulk-sender requirement gaps with exact DNS records to add. Runs on the caller's own Apify account (APIFY_TOKEN) and is billed by Apify pay-per-event; nothing is charged by this server.

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": {
      "domain": "<domain>"
    },
    "name": "check_domain_email_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name, e.g. "example.com" (a URL or email address is accepted and reduced to its domain).
waitSecsNoHow long to wait for results before returning status "running" with a runId (the scan keeps going; use get_audit_results). Default 240.
maxCostUsdNoSpend cap for this run on YOUR Apify account (forwarded to Apify as maxTotalChargeUsd). Default from server config ($2).
dkimSelectorsNoOptional DKIM selectors to test (e.g. "google", "selector1"). Common selectors are tried automatically.

Output Schema

NameRequiredDescriptionDefault
runYes
checkYes
gradeYes
scoreYes
dryRunYestrue = sample data from the built-in mock, NOT a real scan
statusYes"running" = the Actor is still working; call get_audit_results with run.runId later
targetYes
metricsYes
summaryYes
findingsYes
reportUrlNoFull report (HTML/JSON) in the Apify key-value store
datasetUrlNo
findingsTotalYes
severityCountsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, open-world behavior, but the description adds important operational context: it runs on the caller's own Apify account via APIFY_TOKEN and incurs Apify pay-per-event billing. It also explains that the tool returns actionable findings with exact DNS records to add, going beyond the annotations.

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 definition is front-loaded with what is checked, followed by outcome value and billing/auth context. Every sentence contributes distinct information, and the parenthetical lists are dense but not wasteful.

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?

Given the rich input schema, existing output schema, and annotations, the description covers the remaining gaps an agent needs: domain scope, billing/auth implications, and the actionable spoofing/bulk-sender findings. Return-value and async wait behavior are handled by the schema and output schema rather than needing repetition here.

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 all four parameters are already well documented in the input schema, including examples and constraints. The description adds no parameter-specific syntax or format details beyond what the schema provides, so the baseline of 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?

The description states a specific verb and resource: checking a domain's email authentication, deliverability, DNS hygiene, and TLS setup. It enumerates the exact checks (MX, SPF, DKIM, DMARC, BIMI, MTA-STS/TLS-RPT, DNSSEC, CAA, nameservers), making it clearly distinct from sibling website-audit tools.

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 implies when the tool is useful by naming spoofing risk and Gmail/Yahoo bulk-sender gaps, but it does not explicitly say when to use this versus siblings such as full_website_audit or scan_speed_and_revenue. There are no exclusions or explicit alternative-routing instructions.

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