MCPMCP-Tools/Einträge/get_location_directories

get_location_directories

Readlistings:read

The directory/premium-listings table for a SINGLE location (the location's Premium Listings tab): every directory the location is (or can be) listed on, each with its publisher name, connected account, sync status (synced / requires action / never connected) with the error detail, weight tier (very_high / high / medium / low), live URL, whether it needs verification, and `optedOut` — true when the agency has excluded that publisher for this location (see opt_out_publisher_listing). Opted-out rows are HIDDEN by default, exactly as they are for the client: an agency session can pass includeOptedOut: true to see them, which is the only way to find out what has been excluded (a client's own session never sees them, whatever it passes). A row with `excludedForListingSync: true` is still a real directory, but it does not count toward any sync percentage — leave it out of synced/total when you summarise coverage. Also returns cards: connectionScore (% of premium connectors synced), requiresAction count, and the location-info card (name, address, phone, store code). Requires locationId. Read-only. You don't pass an agency — it comes from your credentials, and a location from another agency is never returned. When you tell the user about listing sync, state it as a percentage only; never quote synced/total counts (e.g. never '39/57' or '39 of 57').

Parameter
locationIdstringerforderlich
Location database ID or public loc_ ID (from list_locations or create_location). Accepts the database ID or public loc- ID. IDs must belong to the authenticated agency and permitted client.
includeOptedOutbooleanoptional
Include publishers the agency has opted this location out of (default false — they are hidden, and each returned row carries `optedOut`). Agency sessions only; ignored for a client's own session.
Beispielanfrage
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_location_directories",
    "arguments": {
      "locationId": "string"
    }
  }
}
Beispielantwort
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "..."
      }
    ]
  }
}

Die Antwortform dient nur zur Veranschaulichung — der tatsächliche Inhalt hängt vom Tool und Ihren Daten ab.