Skip to main content
request_domain_overview Request a separately metered supplier summary for a domain or subdomain. Admission is disabled in this build and cannot be configured by retrying. An operator must provide a supported supplier admission path before this command can run. Summaries carry their data mode and provider provenance; they are not link checks or totals derived from selected candidates.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.
Provider-backed admission requires enabled configuration and available allowance; registration alone does not make retrieval available. Inspect usage and the run’s coverage before interpreting results.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Validation and omitted values

includeSubdomains, includeIndirectLinks, excludeInternalBacklinks and backlinksStatus are required. The provider source and internal list limit are server-owned. Current ordinary admission is unavailable. A supported operator configuration is required; retrying cannot activate a supplier.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • v (number, required): must equal 1
  • id (string, required): Resource identifier returned by the operation. pattern: ”^[a-zA-Z0-9_-]{1,128}$”
  • workspace_id (string, required): Workspace that owns this record. pattern: ”^[a-zA-Z0-9_-]{1,128}$”
  • project_id (string, required): Project that owns this record. pattern: ”^[a-zA-Z0-9_-]{1,128}$”
  • operation (string, required): must equal “domain_overview”
  • provider (string, required): values: “linktrail_corpus”, “dataforseo”, “imported”
  • data_mode (string, required): values: “synthetic”, “owned_corpus”, “provider_index”, “imported”
  • query (object, required): additional fields rejected
  • status (string, required): Resource lifecycle status. values: “queued”, “running”, “succeeded”, “failed”, “reconciliation_required”
  • created_at (string, required): UTC timestamp when the record was created. format: “date-time”; pattern: ”^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d\.\d{3}(?:Z))$”
  • started_at (string / null, required).
  • finished_at (string / null, required).
  • error_code (string / null, required): Latest delivery detail code; null when no failure or retry has been recorded.
  • usage (object, required): additional fields rejected
  • result (object / null, required): Saved result; null when this operation has no completed result.
  • coverage (string, required): Dataset scope and completeness, including limits on what these results establish.
  • coverage_scope (string, required): must equal “provider_query”
  • whole_web_coverage (boolean, required): False: these results do not measure the whole web. must equal false
  • replayed (boolean, optional): True when the response reuses an earlier request with the same idempotency value.
Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Continue

get_domain_overview Follow the related workflow, inspect capability status, or return to the command index.