Skip to main content
list_internal_link_scans List retained background website scans for one project. Expired runs are unavailable.
This command name appears in deployment evidence dated 2026-10-16. This page describes current source; read your connected catalog for deployed inputs and access. Workspace scopes and enabled providers still apply.
This read does not start a verification job.

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

Returns up to 20 retained runs for one project; expired runs are excluded. Reads never enqueue capture.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • items (array, required): Records in this bounded page. maxItems: 20
  • limits (object, required): additional fields rejected
Download input schema · Download output schema

Errors and retries

Follow the error recovery before retrying this read. Preserve the selected workspace, project, filters and feed. Recovering a read does not require an idempotency key or another verification job. Operation-specific errors include INTERNAL_LINK_SCANS_UNAVAILABLE, INTERNAL_LINK_SCAN_EXPIRED, SCAN_CONTROL_CONFLICT, SCAN_FINISHED, SCAN_PAGE_LIMIT, INTERNAL_LINK_DAILY_LIMIT, INVALID_CURSOR. 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_internal_link_scan Follow the related workflow, inspect capability status, or return to the command index.