Skip to main content
Glama

Visibility Genies

Read audience breakdown

get_google_analytics_audience_breakdown
Read-only

Sessions and engagement split by device, country, or new versus returning visitors, optionally compared with the previous period. Organic Search by default. Read only and free.

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>"
    },
    "name": "get_google_analytics_audience_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
deviceNoOnly this device: desktop, mobile or tablet.
mediumNoOnly sessions whose medium contains this text, in any case.
offsetNo
sourceNoOnly sessions whose source contains this text, in any case.
channelNoWhich traffic to read: Organic Search only (default) or all.organic_search
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.
breakdownNoHow to split the audience.device
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.
comparePreviousPeriodNoAlso read the period just before and compare the rows.

Output Schema

NameRequiredDescriptionDefault
rowsNo
errorNo
quotaNo
sourceNo
statusYes
requestNo
pageInfoNo
rowCountNo
warningsNo
comparisonNo
diagnosticsNo
totalRowCountNo
reportMetadataNo
ecommerceActivityNo
diagnosticCoverageNo
siteSearchActivityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds a little useful context ('free', default Organic Search scope, optional period comparison), but most of that repeats schema defaults and it says nothing about row limits, pagination, or what the comparison output looks like.

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?

A single compact sentence with the core purpose and the default scope front-loaded, plus a short trailing clause on safety and cost. No filler, though 'Read only and free' partially duplicates the readOnlyHint annotation.

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

Completeness4/5

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

With 16 parameters, 88% schema coverage, annotations, and an output schema, the definition only needs to fix purpose and scope, which it does. The remaining gap is the absence of routing guidance among the many google_analytics siblings, which is desirable but less critical given the rich structured fields.

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 88%, so the schema already explains nearly every parameter, including filters, date pairing, and channelGroup. The description adds only the breakdown dimensions and the Organic Search default, both of which are already documented in the schema, so it does not materially deepen parameter meaning.

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?

States a specific verb+resource: sessions and engagement split by audience dimension, with the dimension options and default scope named. However it lists only device, country, and new-vs-returning while the schema's breakdown enum also offers region and city, and it names no sibling to distinguish it from get_google_analytics_traffic_breakdown or get_google_analytics_traffic_acquisition.

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?

The description implies usage through scope statements ('Organic Search by default', 'optionally compared with the previous period') but gives no explicit when-to-use or when-not-to-use guidance. With closely related siblings like traffic_breakdown and organic_overview present, an agent must infer which one answers an audience-segmentation question.

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