Skip to main content
Glama
Sign In

Google Analytics 4 MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

GA4 Setup Helper

query_contexts
Read-only

Helper for planning InsightfulPipe Google Analytics data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, property_id, other source metadata, AND available_requests (all tables you can query).

Step 2: request='actions_details' with actions=['table_a', 'table_b'] – REQUIRED before querying. Returns the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

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": {
      "request": "<request>"
    },
    "name": "query_contexts"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionsNo
requestYes
brand_idNo
platformNo
property_idNo
workspace_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description's main added value is explaining what each mode returns and why actions_details is required before querying. It discloses returned metadata, available requests, request bodies, identifiers, fields, time ranges, and notes, but does not discuss auth or rate-limit behavior.

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

Conciseness5/5

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

The description is front-loaded, organized as numbered steps, and every sentence contributes to the workflow or clarifies an optional mode. The note that available_actions is already included in accounts is useful and avoids unnecessary calls.

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?

Given that an output schema exists, the description does not need to specify return shapes in full, but it still gives useful return-content context. It covers the main workflow well, with only minor gaps around platform and property_id as input parameters.

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 0%, so the description must carry parameter meaning. It explains the request enum values, the actions array format, and brand_id plus workspace_id for the brands mode, but it leaves platform and property_id input semantics unexplained.

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 clearly states that this is a planning/setup helper for Google Analytics queries and enumerates its request modes. It distinguishes itself from direct query execution by framing itself as a prerequisite ('REQUIRED before querying'), though it does not explicitly name or contrast with the sibling tools query_data or execute_action.

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

Usage Guidelines4/5

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

It provides an explicit sequence: first request='accounts', then request='actions_details' with actions, and labels actions_details as required before querying. Optional calls are also explained, but there is no direct mention of when to prefer this tool over query_data or execute_action by name.

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

All Google Analytics 4 MCP by InsightfulPipe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources