Skip to main content
Glama

Visibility Genies

Read traffic breakdown

get_google_analytics_traffic_breakdown
Read-only

The Traffic Insights tabs from Google Analytics, with the same numbers as the page: channels (channel, source and medium, or campaign), ai_assistants (visits from AI assistants by source, landing page or key event), key_events, countries_devices (country, device, region or city) and pages. Every row comes with the period before it and the totals, and the text says when Google sampled, hid or folded numbers. Read only and free. Defaults to the last 28 complete property days.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "tab": "<tab>"
    },
    "name": "get_google_analytics_traffic_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabYesThe Traffic Insights tab: channels, ai_assistants (visits from AI assistants), key_events, countries_devices or pages.
groupNoHow the tab groups its rows. channels: channel_group, source_medium, campaign; ai_assistants: source, landing_page, key_event; key_events: event, event_and_landing_page; countries_devices: country, device, region, city; pages: page. The first one of the tab is the default.
deviceNoOnly this device: desktop, mobile or tablet.
mediumNoOnly sessions whose medium contains this text, in any case.
sourceNoOnly sessions whose source contains this text, in any case.
countryNoOnly this country, as its two-letter ISO code, for example DE.
endDateNoInclusive date as YYYY-MM-DD. Give both startDate and endDate, or neither for the last 28 complete property days.
campaignNoOnly sessions whose campaign contains this text, in any case.
keyEventNoCount only this key event (for example purchase) in the key event columns, instead of all key events. Not for the key events report, which lists them by name.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoInclusive date as YYYY-MM-DD. Give both startDate and endDate, or neither for the last 28 complete property days.
channelGroupNoOnly this Google default channel group by its exact name, for example Paid Search, Organic Social or AI Assistant. Pass channel=all where the tool has it, or Organic Search is all that is read.
pageContainsNoOnly pages whose address contains this text, in any case. Not for site search or ecommerce by item.

Output Schema

NameRequiredDescriptionDefault
rowsNo
errorNo
groupNo
stateNo
foldedNo
periodNo
statusYes
totalsNo
metricsNo
sampledNo
truncatedNo
thresholdedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (readOnly, openWorld, non-destructive), the description adds real behavioral context: every row ships with the prior period and totals, and the response text flags when Google sampled, hid or folded numbers. It also states the call is free and defaults to the last 28 complete property days, which matters for billing and date handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The tab inventory is front-loaded and each clause carries information (tab scope, comparison columns, data-quality caveats, date default). The middle sentence is dense and parenthetical-heavy, but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter tool with full schema coverage and an output schema, the description covers what the agent still needs: which tabs exist, how rows are structured with prior-period comparison, sampling caveats, and the default date window. Return values need not be explained given the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the schema itself already documents the group defaults, filter semantics and the keyEvent caveat, so the description only restates the tab/group taxonomy ('channels: channel, source and medium, or campaign'). Baseline 3 is appropriate; it adds little parameter meaning the schema does not already carry.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely and enumerates the five tabs it covers (channels, ai_assistants, key_events, countries_devices, pages), so an agent knows exactly what data comes back. It does not, however, say how it differs from nearby siblings such as get_google_analytics_traffic_acquisition or get_google_analytics_page_performance, leaving overlap resolution to the agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the tab list plus the default window ('last 28 complete property days') tells the agent this is the general traffic reporting call, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for narrower questions. The agent must infer routing from sibling names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources