Skip to main content
list_search_connections Read configured search providers and saved connection status for one website. No credentials are returned.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers 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

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

Select one accessible project. The response lists public connection status and whether each provider is configured; it returns no provider credentials. Google supplies search-performance rows. Bing supplies sampled backlink rows. Browser consent, property selection, disconnect and forgetting require a signed-in workspace owner or administrator. Google backlinks use Search Console browser exports and the existing import workflow. A Google account connection does not read the Links report.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • connections (array, required).
  • providers (array, required).
Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. 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 · sync_search_connection Follow the related workflow, inspect capability status, or return to the command index.