Skip to main content
Glama

Visibility Genies

Read page performance

get_google_analytics_page_performance
Read-only

Page views, active users, engagement time and key events per page from Google Analytics. Organic Search by default; pass channel=all for every channel. 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_page_performance"
  }
}

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.
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.
includeDateNoSplit each page by date.
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
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=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description's "Read only and free" mostly restates that, though "free" does add a cost signal absent from annotations. The default Organic Search scoping is a real behavioral fact worth stating, but pagination, result caps and quota behavior are left unmentioned.

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?

Two tight sentences, front-loaded with the returned metrics followed by the default-scope caveat; nothing is buried. "Read only and free" is the only phrase that marginally overlaps with the annotations.

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 an output schema present and 13 of 15 parameters described in the schema, the description need not explain return values or argument formats. For a 15-parameter analytical read, it covers the scope decision that matters most and leaves the rest to 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 coverage is 87%, so nearly every parameter is already documented, and the description's channel note largely duplicates the schema's own channel description. It adds no guidance on how limit/offset interact or on the startDate/endDate pairing beyond what the schema says.

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?

"Page views, active users, engagement time and key events per page from Google Analytics" gives a specific verb-less but concrete resource plus the exact metrics returned, so an agent knows what comes back. It stops short of distinguishing itself from siblings like get_google_analytics_organic_landing_pages or get_google_analytics_traffic_breakdown, which also read GA traffic data.

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 tells the agent how to widen scope ("pass channel=all for every channel") and states the default is Organic Search, which is genuinely useful routing guidance. It never says when to pick this page-level report over the sibling landing-page or traffic-breakdown reports, so the choice between them stays implicit.

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