Skip to main content
Glama
Sign In

GSCPAP - Google Search Console, GA4, PageSpeed Insights & live SERPs MCP

by com.gscpap
OverviewDiscussionsAdmin

List GA4 properties

list_ga4_properties
Read-only

List every Google Analytics 4 account + property the user can access.

Always call this first when working with GA4 - the AI needs a property_id to pass to every other ga4_* tool. Returns the full account+property tree in one round-trip:

[
  {"account": "accounts/123",
   "display_name": "My Company",
   "properties": [
     {"property": "properties/302550400",
      "display_name": "Main Site",
      "property_type": "PROPERTY_TYPE_ORDINARY",
      "parent": "accounts/123"}
   ]},
  ...
]

If the user has no GA4 properties (or only Universal Analytics), the properties list is empty.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds real behavior: the call returns the full account+property tree in a single round-trip, and the properties list is empty when the user has no GA4 (or only Universal Analytics). The inline sample payload is somewhat redundant with the existing output schema, which slightly dilutes the added value.

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?

Front-loaded with the prerequisite, then the return contract, then the empty-result edge case. The multi-line JSON block is the largest chunk and duplicates the output schema, so a sentence describing the tree shape would have been leaner, but nothing is truly wasted.

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 zero-parameter discovery tool with annotations and an output schema, everything an agent needs is present: when to call it, why (to obtain property_id), what comes back, and how the empty case reads. No open questions remain before invoking it.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline applies. The description correctly spends no words on arguments and instead spends them on prerequisites and return shape.

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

Purpose5/5

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

States a specific verb and resource ('List every Google Analytics 4 account + property') and scopes it to what the user can access. It is immediately distinguishable from the ga4_* siblings because it declares itself the discovery step that produces the property_id those tools require.

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

Usage Guidelines5/5

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

Explicit precondition: 'Always call this first when working with GA4 - the AI needs a property_id to pass to every other ga4_* tool.' That is both a when-to-use and a routing rule to the sibling family, with no ambiguity left to infer.

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

All GSCPAP - Google Search Console, GA4, PageSpeed Insights & live SERPs MCP 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