Google Analytics MCP tools: run_report, run_realtime_report and the rest

The tools at a glance

The server is googleanalytics/google-analytics-mcp. It is read-only by default and talks to two Google APIs: the Google Analytics Admin API and the Google Analytics Data API. Seven of its tools only read, and they are the ones this page covers.

Every tool except get_account_summaries takes a property_id, either a number or a string like properties/123456. Find yours with get_account_summaries.

get_account_summaries

get_account_summaries retrieves information about your Google Analytics accounts and properties. It takes no parameters. An assistant usually calls it first, to find the property_id the other tools need.

get_property_details

get_property_details returns details about one property. Its only parameter is property_id (required).

run_report

run_report runs a Google Analytics Data API report: the historical numbers, such as sessions by channel last month. Its parameters:

• property_id, date_ranges, dimensions and metrics are required. Dimensions and metrics are lists of names, for example sessionDefaultChannelGroup and sessions.
• Optional: dimension_filter and metric_filter (Data API FilterExpression objects), order_bys, limit, offset for paging, currency_code (ISO 4217) and return_property_quota.

If the assistant doesn't know which custom fields your property has, it should call get_custom_dimensions_and_metrics first.

run_realtime_report

run_realtime_report runs a realtime report: what is happening on the property now, rather than over a date range. Google Analytics 4's Realtime report covers the last 30 minutes (see real-time website analytics). Its parameters:

• property_id, dimensions and metrics are required. The repository says dimensions and metrics must be realtime ones, so a name that works in run_report can fail here.
• Optional: dimension_filter, metric_filter, order_bys, limit (a positive integer up to 250,000) and return_property_quota.
• The tool also exposes an offset parameter, but a nonzero value currently fails: the wrapper sets offset on the request, and the Data API's realtime request has no such field. Leave it unset.
• There is no date_ranges parameter. That is what separates it from run_report.

run_funnel_report

run_funnel_report runs a Data API funnel report, which shows how many people get from one step to the next. Its parameters:

• property_id and funnel_steps (a list of steps, each with a name and filter criteria) are required.
• Optional: date_ranges, funnel_breakdown, funnel_next_action, segments and return_property_quota.

get_custom_dimensions_and_metrics

get_custom_dimensions_and_metrics returns a property's custom dimensions and custom metrics as two lists, custom_dimensions and custom_metrics. Its only parameter is property_id (required). Use it before run_report when a report needs a field you defined yourself.

list_google_ads_links

list_google_ads_links returns the links from a property to Google Ads accounts. Its only parameter is property_id (required).

Two more tools in the repo: annotations

The repository also has list_property_annotations, which reads the notes left on a property for dates or periods, and create_property_annotation, which writes one. The second needs the --allow-write flag and the analytics.edit scope. Everything else needs only https://www.googleapis.com/auth/analytics.readonly, plus Application Default Credentials.

When an assistant prints the tool name instead of running it

If you see run_report or run_realtime_report in the chat and no numbers, the assistant named the tool but the call did not run or did not return. Try these in order:

1. Ask again and tell it to run the tool and show the rows.
2. Check the Google Analytics MCP server is connected in your assistant's tool or connector settings.
3. Check the Google Analytics Admin API and Data API are enabled in the Google Cloud project your credentials belong to.
4. Check your credentials carry the analytics.readonly scope and can see the property. Run get_account_summaries to confirm the property is listed.
5. If the error is about a field, use a realtime dimension or metric for run_realtime_report.

These steps are general. Each assistant reports tool failures in its own way, so read the message it shows.

See live visitors and revenue by channel without the API

The usual reasons to call run_realtime_report and run_report are two questions: who is on my site right now, and which channel brings the money. Stickybeak answers both on screen, with no Google Cloud project, credentials or tool calls. One script tag gives you live visitors; revenue needs a purchase event sent after each order.

• Live visitors. The wall shows every site you own on one screen, with visitors now, a per-minute chart and top countries.
• Revenue by channel. Revenue is tied to the channel, campaign or ?ref= code it came from. Revenue attribution needs purchase events with server-verified order values (see revenue attribution) and starts on the Solo plan ($20 a month); the free plan covers up to 10k pageviews a month.

Stickybeak does not have an MCP server yet; its pricing page lists MCP as on the way. If you want an assistant to query Google Analytics today, the server above is the route. See Google Analytics alternatives if you are weighing a switch.

Sources: tool names, parameters, scopes and setup read on 31 October 2026 from the googleanalytics/google-analytics-mcp repository (its README and the source files for each tool). Stickybeak facts come from this site's pricing page. The repository changes; if a name or parameter here is out of date, tell us and we will fix it.