Skip to main content
get_link_reports Read profile and anchor reports from one saved dataset snapshot. Coverage stays limited to monitored placements.
Name recorded in the 2026-10-17 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access 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

Schema-validated example; IDs and dates are illustrative. 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

Omitting projectId reads the accessible workspace scope rather than selecting a different project. These are bounded reports, not cursor-paginated exports. The report limit bounds returned groups; retained dataset coverage and truncation remain explicit. Omitted projectId includes records allowed by the credential. Profile, anchor and follow reports use one saved dataset snapshot. follow.links counts watches with included retained occurrences after the report row and byte limits. A later unknown attempt can leave earlier conclusive observations in this dataset; read coverage and observation dates. The direct HTTP GET /v1/reports/links accepts links=all (the default) or links=live to select watches counted as live by get_link_summary. This query parameter is absent from the strict generic command input, including CLI and MCP calls, and from the profile and anchor resource routes.

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.
  • profile (object, required).
  • anchors (object, required).
  • follow (object, optional): Follow categories for watched links with eligible retained occurrences in this bounded report. These categories describe observed rel tokens and do not infer ranking credit.
Types, allowed values, limits and nested fields:
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. 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

export_link_watches Follow the related workflow. See capability status for availability or the command index for another operation.