get_target_placements
List placements whose configured target URL exactly matches this destination. Other URLs matched by a domain/path watch are not included.
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 instructuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.
Response formats
format selects the row shape. detailed is the example above: every field. concise keeps, per row: id, source_url, target_url, target_scope, status, state; every top-level field (cursors, counts, coverage, metadata) is kept in both. The observation state an unknown-versus-absent decision depends on is never dropped. MCP and code mode default to concise; the CLI and HTTP default to detailed; the response names the default it applied in defaults_applied.
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
Omit cursor for the first page. Keep continuation cursors opaque and use them only with the same listing and filters. Pages are ordered by creation time, then identifier, ascending. Matches the watch target URL exactly. It does not include other URLs that a domain/path watch could match.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