opt_out_publisher_listing
Exclude ONE publisher/directory from ONE location's listings. To the client the listing stops existing: it disappears from their portal, from the location's Listings overview, and from every count, score and denominator — so a directory the agency has decided not to work on stops dragging the client's numbers down. OS also stops syncing it: no new listing work is created for that publisher, and work that has been queued but not yet sent to the directory is canceled (the ids come back as `canceledOrderItemIds`). What it does NOT do: it never contacts the publisher, so a live listing already on their site stays up and unchanged, and the location's connected account for that publisher is left alone — nothing is disconnected, deleted or unpublished. Nothing is thrown away either: the row keeps its status, live link, connection and history, so opt_in_publisher_listing puts it back exactly as it was rather than starting over. This is per location. To exclude a publisher for an entire client, change the client's publisher set instead (list_publisher_sets / update_publisher_set) — and note the publisher set always wins: if the set already excludes a site, opting back in here cannot restore it. Identify the location by its id (from list_locations), and the publisher either by name (google | facebook | apple | bing) or, for any other directory, by its numeric siteId (from list_sites). Requires an identified agency user — the change is recorded in the audit trail against the person who made it.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "opt_out_publisher_listing",
"arguments": {
"locationId": "string"
}
}
}{
"jsonrpc": "2.0",
"id": 1,
"result": {
"content": [
{
"type": "text",
"text": "..."
}
]
}
}La forme de la réponse est indicative — le contenu réel dépend de l'outil et de vos données.