Skip to main content
Glama

kadi_bence/domain-whois-lookup

kadi_bence--domain-whois-lookup
Destructive

This tool calls the Actor "kadi_bence/domain-whois-lookup" and retrieves its output results. Actor description: $1.50 per 1,000 domains. Look up domains via official RDAP (WHOIS). Input: list of domains; optional DNS records. Returns per domain: registered, registrar, creation and expiry dates, domain age, nameservers, status, DNSSEC, plus DNS/MX/SPF/DMARC. 1,100+ TLDs, no personal data, no API key.

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": {
      "domains": "<domains>"
    },
    "name": "kadi_bence--domain-whois-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYes**REQUIRED** One per line (commas and semicolons also split). Domains, URLs and e-mail addresses are reduced to the registrable domain, e.g. https://news.example.co.uk/page -> example.co.uk, info@example.de -> example.de. Duplicates are skipped; IP addresses and public suffixes (gov.uk) are rejected. You can paste thousands of lines from a CSV column. Example values: ["apify.com","wikipedia.org","https://www.bbc.co.uk/news","www.spiegel.de","github.io","afnic.fr","sidn.nl","cbc.ca"]
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
includeDnsNoAdd A, AAAA, MX, NS and TXT records, SPF and DMARC checks and the e-mail provider (Google Workspace, Microsoft 365...) via DNS-over-HTTPS. Included in the price. Turn off if you only need dates and registrar, e.g. for an expiry check. Example values: true
maxResultsNoStop after this many domains (0 = all, up to 100,000 per run). Tip: use 10-20 to test a big list first.
onlyAvailableNoKeep only names the registry reports as not registered and that don't resolve in DNS (availability = possibly_available), e.g. to check a list of name ideas. Registered domains are skipped and not charged. Not-registered rows are always free. Always confirm at a registrar before buying.
maxConcurrencyNoHow many domains are looked up at the same time (1-50). Each registry still gets its own polite rate limit, so a higher value mostly helps lists that mix many TLDs; a list of only .org domains won't get much faster. Example values: 10
expiringWithinDaysNoKeep only registered domains whose expiry date is at most this many days away (or already passed), e.g. 30 for a renewal check of your portfolio or 90 to find soon-expiring names. 0 = off. Domains without an expiry date in RDAP (e.g. .de) are skipped. Skipped domains are not charged.
requestTimeoutSecsNoGive up on a slow registry server after this many seconds (5-60). Busy servers and dropped connections are retried up to 3 times; domains that still fail are listed with an error and not charged. Example values: 20

Output Schema

NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / expiringWithinDays
      Added value: +{
      +  "default": 0,
      +  "description": "Keep only registered domains whose expiry date is at most this many days away (or already passed), e.g. 30 for a renewal check of your portfolio or 90 to find soon-expiring names. 0 = off. Domains without an expiry date in RDAP (e.g. .de) are skipped. Skipped domains are not charged.",
      +  "title": "Only domains expiring within (days)",
      +  "type": "integer"
      +}
    • addedInput schema / properties / onlyAvailable
      Added value: +{
      +  "default": false,
      +  "description": "Keep only names the registry reports as not registered and that don't resolve in DNS (availability = possibly_available), e.g. to check a list of name ideas. Registered domains are skipped and not charged. Not-registered rows are always free. Always confirm at a registrar before buying.",
      +  "title": "Only available domains (availability checker)",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / updatedDate / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "aRecords": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "aaaaRecords": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "availability": {
      +      "type": "string"
      +    },
      +    "createdDate": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "daysUntilExpiry": {
      +      "type": [
      +        "null",
      +        "number"
      +      ]
      +    },
      +    "dmarcPolicy": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "dnsResolved": {
      +      "type": "boolean"
      +    },
      +    "dnssec": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "domain": {
      +      "type": "string"
      +    },
      +    "domainAgeDays": {
      +      "type": [
      +        "null",
      +        "number"
      +      ]
      +    },
      +    "domainUnicode": {
      +      "type": "string"
      +    },
      +    "emailProvider": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "error": {
      +      "type": "null"
      +    },
      +    "errorType": {
      +      "type": "null"
      +    },
      +    "expiresDate": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "hasDmarc": {
      +      "type": "boolean"
      +    },
      +    "hasSpf": {
      +      "type": "boolean"
      +    },
      +    "input": {
      +      "type": "string"
      +    },
      +    "lookedUpAt": {
      +      "type": "string"
      +    },
      +    "lookupSource": {
      +      "type": "string"
      +    },
      +    "mxRecords": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "nameservers": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "nsRecords": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "registered": {
      +      "type": "boolean"
      +    },
      +    "registrantCountry": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "registrantOrganization": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "registrar": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "registrarAbuseEmail": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "registrarAbusePhone": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "registrarIanaId": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "registrarUrl": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "registryDomainId": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "registryServer": {
      +      "type": "string"
      +    },
      +    "registryTermsUrl": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "status": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "tld": {
      +      "type": "string"
      +    },
      +    "txtRecords": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "updatedDate": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.9/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 ($1.50 per 1,000 domains, DNS included, skipped and failed domains not charged), registry-specific polite rate limits, up to 3 retries on failure, and that failures surface as per-domain errors without billing. These are exactly the operational facts an agent needs before invoking a paid, open-world run. The only minor tension is that the phrasing 'look up' reads as read-only while destructiveHint is true, but that is explainable by the paid actor run being launched, not by a factual contradiction.

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?

The actor summary is dense and front-loads cost, coverage, inputs and outputs in effectively three compact clauses. The opening boilerplate ('This tool calls the Actor ... and retrieves its output results') is pure wrapper text that delays the actual purpose. Otherwise there is no padding.

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?

An output schema exists, yet the description still helpfully previews returned fields, and it covers cost, scale limits and failure handling for an eight-parameter paid tool. What is missing is any routing guidance relative to the sibling audit and extraction tools in the same namespace. For a single-purpose bulk lookup, that omission is the main residual gap.

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 the schema already documents all eight parameters thoroughly, and the description only summarizes 'input: list of domains; optional DNS records'. That summary is accurate but adds no syntax, defaults, or edge-case meaning beyond the schema. Baseline 3 applies when the schema is doing the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: bulk domain lookup via official RDAP/WHOIS, covering 1,100+ TLDs. It also enumerates the returned fields (registrar, dates, age, nameservers, status, DNSSEC, DNS/MX/SPF/DMARC), which pins the tool's identity precisely. It does not, however, contrast itself against siblings like seo-site-audit or company-intelligence, leaving differentiation to the tool name.

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?

Usage context is only implied: the description notes DNS records are 'optional' and that pricing is per domain, which hints at when to enable or disable them. There is no explicit statement of when to choose this tool over a sibling, nor any stated preconditions or exclusions at the tool level. Satisfying guidance lives mostly in the parameter descriptions rather than the tool description.

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.