MCPMCP Tools/Listings/get_profile_analytics_rollup

get_profile_analytics_rollup

Readlistings:read

Profile analytics aggregated across ALL of a client's locations (the Listings → All locations → Profile Analytics view): profile views, all actions, website visits, phone calls, direction requests, button clicks, followers, post engagement across the client's connected publishers (Google, Facebook, Apple, Bing), plus a followers gauge and data-coverage across locations. Also returns a per-location `leaderboard` (top locations by profile views, with Δ% vs the prior window and a sparkline). Client-scoped — requires clientId (no locationId). Optional from/to (ISO), sources (subset of google/facebook/apple/bing), comparison (vs a prior window), granularity, leaderboardLimit (top-N locations, default 25, max 100), leaderboardSearch (filter leaderboard by location name). Defaults to the last 30 days. Read-only — data is served from the aggregation tables (refreshed daily by background jobs). You don't pass an agency — it comes from your credentials, and a client from another agency is never returned.

Parameters
clientIdstringrequired
Client id (from list_clients)
fromstringoptional
Window start (ISO); default 30 days ago
tostringoptional
Window end (ISO); default now
sources("google" | "facebook" | "apple" | "bing")[]optional
Publishers to include (default all).
comparison"none" | "previous_period" | "previous_month" | "previous_quarter" | "previous_6_months" | "custom"optional
Compare vs a prior window.
granularity"daily" | "weekly" | "monthly"optional
Time bucket.
leaderboardLimitnumberoptional
Top-N locations in the leaderboard (1-100, default 25)
leaderboardSearchstringoptional
Filter the leaderboard by location name
Example request
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_profile_analytics_rollup",
    "arguments": {
      "clientId": "string"
    }
  }
}
Example response
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "..."
      }
    ]
  }
}

Response shape shown for illustration — the actual content depends on the tool and your data.