Skip to main content
get_client_link_report Read a one-page client link report for one website: live links now, plus links new, back, lost, went missing, changed and won in a calendar month or the last 1-90 days, each with its last check and evidence observation. Counts match get_link_summary and the Changes page. Won counts distinct saved prospects a check verified live in the period. Outreach claims alone do not count. Requires watches:read and events:read; reads only.
Hosted availability unverified: this name is absent from the 2026-10-27 deployment evidence. Check your connected catalog before calling. 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

Requires watches:read and events:read. Supply one accessible website id and either month (YYYY-MM, a UTC calendar month that has started) or days (1 to 90, default 30), not both. days covers that many UTC calendar days including today, the same period get_link_summary uses, so new plus back equals its found and lost equals its lost. live and the other link states are read at the time of the report, with get_link_summary’s status rule. new, back, lost, went_missing and changed count retained change events recorded in the period, the same events the Changes page lists; changed is placement_changed (link text, rel or page directives changed while the link stayed live). A never-observed link is not lost, and an unknown check is not a removal. won counts saved prospects a check found live in the period (prospect_won: the check saw the link present with complete evidence), dated by that check; each won link is also one of the period’s new links. An outreach status set by hand, a reply, a promise or a claimed publication is never a win. counts.links equals get_link_summary’s links; counts.prospects are saved prospects inside it, which are not monitored links yet and have no link state. Each section lists at most limit links (1 to 200, default 50), newest change first, with the latest check and the observation behind it; truncated says when the total is larger. Change counts examine at most the latest 100,000 workspace event positions, and a retention floor or that cap makes coverage.changes_complete false. branding only labels the report (agentlinkops, agency with a name, or none). The report reads saved monitoring records only. It starts no check, crawl, supplier request or outreach, and it is not a whole-web backlink count.

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.
  • schema_version (number, required).
  • workspace_id (string, required): Workspace that owns this record.
  • project (object, required).
  • generated_at (string, required).
  • period (object, required).
  • branding (object, required).
  • counts (object, required).
  • won (object, required).
  • sections (object, required).
  • coverage (object, required): Dataset scope and completeness, including limits on what these results establish.
  • notes (array, required).
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. Operation-specific errors include INVALID_CLIENT_REPORT_INPUT, CLIENT_REPORT_PERIOD_IN_FUTURE, PROJECT_NOT_FOUND, WORKSPACE_ACCESS_DENIED, INSUFFICIENT_SCOPE. 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_link_summary · get_link_change_report · list_link_watches Follow the related workflow. See capability status for availability or the command index for another operation.