Skip to main content
get_client_results_report Read client results for up to 10 websites, each its own population: earned (found by a check in the period, including a link found again) with how each link entered monitoring and its recorded outreach dates, retained, recovered, lost, went missing, changed, never live and won, plus loss, recovery, change and lasting can’t-reach review groups with evidence observations. A calendar month or the last 1-90 days. No competitor cohort is compared. 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 1 to 10 distinct accessible website ids and either month (YYYY-MM, a UTC calendar month that has started) or days (1 to 90, default 30), not both. Each website is reported as its own population; nothing is pooled or summed across websites, and no competitor cohort is compared (comparison.state is no_comparable_cohort_yet). earned counts found changes in the period (the Changes page’s New; a link found again after removal counts again) and equals get_client_link_report’s new for the same website and period. earned_by_origin splits it by how each link entered monitoring: import, discovery_candidate, prospect_pipeline or direct_or_unrecorded. Origin does not say who earned a link, and an imported link is not proof that recorded outreach earned it. Each listed earned link carries its saved outreach record (status, last_contacted_at and campaign, as the prospect pipeline holds them) and verified_win_at, the last check that found it live as a won prospect; outreach is null when none is saved. earned_with_verified_outreach counts earned links found as won prospects and equals earned_by_origin.prospect_pipeline. Only a check-verified prospect counts as won; a saved status is a record, not a win. retained counts links live at the period’s start and end with no lost or went-missing change in between, from recorded found, back, lost and went-missing changes; coverage.retained_complete is false when older changes are outside the retained feed. recovered is back in the period. never_live counts monitored links no check has seen present; they are never lost. Saved and retired prospects are not monitored links and are never counted as never live; counts.prospects reports saved prospects on their own. retained counts only non-archived monitored links. couldnt_check is the current unknown count. review lists lost, recovered, went_missing, changed and cant_reach_lasting (can’t reach for more than 7 days) links, at most limit each, with the latest check and evidence observation. Review groups do not diagnose negative SEO, prescribe a disavow or claim ranking or traffic effects. Reads saved records only and starts no check, crawl or supplier request.

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.
  • generated_at (string, required).
  • period (object, required).
  • sites (array, required).
  • comparison (object, required).
  • 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_client_link_report · get_evidence · get_link_locator Follow the related workflow. See capability status for availability or the command index for another operation.