get_listing_issues

What blocks a location's listings, as a deduplicated list of FIXES (not listings): each issue is one edit, sign-in or outside step, with `problem`, `tier` (1 blocks publishing, 2 a rejected update, 3 preventive/unidentified), `fix` (edit section/field/tab, connect, account renew, verify, external link, or explain), `capability` (whether this caller may start it, and why not), `publishers` it would unblock and `state` (`update_in_flight` = a newer send is pending, not fixed). `reasonKey` is the publisher's reason as a message key; `reason` is its English text. With `locationId`: that location, complete. Without: a roll-up across the client (or the agency), read in pages of locations — keep calling with `cursor: page.nextCursor` and the SAME other arguments until `page.nextCursor` is null (`page.lastPage` true). `complete` and `totals` are set only when one call covered the whole scope; across several pages `totals` stays null, so never present a page's counts as the total — merge the pages' issues by `id`, fixes by `fixKey` and groups by `groupKey`, then count. `groups` folds the same problem across locations; one shared account is one group and one fix whatever each location's symptom. `clientName`/`locationCity` tell same-named locations apart. Read-only: nothing is fixed, retried or sent by this call.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_listing_issues",
    "arguments": {}
  }
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "..."
      }
    ]
  }
}