schedule_internal_link_scans
Set weekly or monthly rescans of one website, or off. Each scheduled scan runs like start_internal_link_scan under your current access; its changes view compares it with the previous scan.
This command name is absent from deployment evidence dated 2026-10-17. 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 instructuredContent 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
Sets weekly or monthly rescans for one website, or turns them off. One schedule per website; the first scheduled scan starts one cadence after the newest scan, or at once when there is none. Each scheduled scan runs like start_internal_link_scan with the current access of the member who set the schedule; revoked access, a changed website address or a workspace without background scans ends the schedule. Scans count toward the shared daily page allowance and wait while an earlier scan is still open. Each finished scan’s view=changes compares it with the previous finished scan for pages both scans checked.Output fields
Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
Download input schema · Download output schema
Errors and retries
This write is annotated idempotent without a caller-supplied idempotency key. Reconcile saved state after an uncertain response, then use the same inputs for the same intended operation. Do not add an unsupported key. Operation-specific errors includeINTERNAL_LINK_SCANS_UNAVAILABLE, SCAN_SCHEDULE_UNAVAILABLE, INVALID_INPUT.
See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.