Skip to main content
Glama

Visibility Genies

Read ecommerce performance

get_google_analytics_ecommerce_performance
Read-only

Ecommerce results from Google Analytics by item or by landing page: transactions and revenue. 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_ecommerce_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.
breakdownNoReport by product item, or by landing page.item
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.
onlyWithTransactionsNoLeave out rows that had no transactions.

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

B3.4/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 the safety profile is covered. The description adds only 'free' (no cost implication) and the default channel, and says nothing about pagination, date-range behavior, or result shape. Note a mild tension: the schema says the project 'is billed to' while the description says 'free'.

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?

Three short sentences with the resource and metrics front-loaded and zero filler. 'Read only' partially duplicates the readOnlyHint annotation, a minor redundancy.

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

Completeness3/5

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

An output schema exists and the input schema is well documented, so the description needn't explain return values. However, for a 16-parameter tool the description omits date-range defaults, the required projectId prerequisite, and how the many filters interact, leaving the agent to rely entirely on the 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 coverage is 88%, so the schema already documents nearly all 16 parameters including the breakdown and channel enums. The description restates the item/landing_page breakdown and the organic_search default but adds no syntax, interaction, or constraint detail beyond what the schema provides; baseline 3 applies.

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+metrics: ecommerce results from Google Analytics with transactions and revenue, broken down by item or landing page. This distinguishes it reasonably well from page-level or traffic-oriented siblings, though it never names an alternative tool.

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 'Organic Search by default' note gives the agent the default scope, which affects interpretation of results, but there is no explicit when-to-use or when-not guidance versus tools like get_google_analytics_page_performance or get_google_analytics_organic_landing_pages.

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