Skip to main content
process_internal_link_snapshot Independently capture up to three pending inventory pages with robots and public-network protections. Repeated calls resume; no recurring monitoring, rendering or site edits. Prefer one page per call for interactive clients.
This command name is absent from deployment evidence dated 2026-09-20. Hosted availability for this current definition is unverified; inspect your connected catalog before invoking it. Verify the command and its input schema in the selected environment.
This operation changes saved state. Review its inputs and retry behavior before calling.

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

Requires watches:read and watches:write. Each call attempts up to maxPages pending pages, from one to three, within request and publisher pacing limits. It can return before that many pages finish. No recurring monitor, browser rendering or website edit starts. Repeated calls can capture more pending pages, so processing is not an idempotent replay. After a timeout, read get_internal_link_snapshot before deciding whether to resume the same snapshot. A complete snapshot returns without new capture. A busy snapshot or publisher cooldown can return progress with no new capture. Respect snapshot.retryAfterSeconds and any returned retryAt before retrying. Unknown or interrupted captures remain unknown; they do not establish missing links. Limits include 300 admitted pages per workspace UTC day, 2 MiB per page, 200 retained edges per page and 30-day snapshot retention. Acquisition follows robots and public-network restrictions; coverage describes raw HTML only.

Defaults when omitted

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • snapshot (object, required): additional fields rejected
  • limits (object, required): additional fields rejected
  • retryAt (string / null, optional).
Download input schema · Download output schema

Errors and retries

This write is not annotated idempotent. After a timeout, inspect existing state before repeating it. Operation-specific errors include INVALID_INPUT, PROJECT_ACCESS_DENIED, INTERNAL_LINK_SNAPSHOT_NOT_FOUND, INTERNAL_LINK_SNAPSHOT_EXPIRED, INTERNAL_LINK_SCOPE_MISMATCH, INTERNAL_LINK_LEASE_LOST, INTERNAL_LINK_DAILY_LIMIT, INTERNAL_LINK_SCOPE_DELETING. 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_snapshot · query_internal_link_snapshot Follow the related workflow, inspect capability status, or return to the command index.