Skip to main content
sync_search_connection Refresh the selected Google performance property or Bing backlink sample. Requires a browser-approved connection. This does not enroll monitoring.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.
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

A human administrator must first connect the provider and select an accessible property covering the project. Agents with discovery:write can then request a bounded sync. Google returns page/query performance for the reader date window. Bing returns sampled inbound links with collection coverage. Provider data does not start monitoring. Omit continue to start a fresh collection. Use continue:true only when Bing coverage.nextProviderCursor indicates another provider batch and coverage.limitReached is false. Continuation appends to the same snapshot and preserves earlier row IDs; the saved snapshot holds at most 10,000 rows. A fresh sync replaces the saved snapshot. Import any rows you need before starting a new collection.

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. Download input schema · Download output schema

Errors and retries

This command is not annotated idempotent. After a timeout, inspect existing state before repeating a write. 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

list_search_connection_rows · import_search_connection_rows Follow the related workflow, inspect capability status, or return to the command index.