Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ga_list_properties

Read-only

Lists Google Analytics 4 accounts and properties accessible to the signed-in Google account, including property IDs, so you can identify targets for reporting or analysis.

Instructions

List the Google Analytics 4 accounts and properties this Google account can access (with property IDs).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ga_list_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=true annotations already tell the agent this is a safe, external read, so the description needs only to add context. It usefully discloses that results include property IDs (a concrete payload detail), but says nothing about the shape, nesting, or size of the account/property hierarchy.

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?

A single sentence with no wasted words, leading with the verb and resource and ending with the payload detail. Nothing is redundant.

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?

For a zero-parameter discovery tool with no output schema, the definition covers what is listed and that property IDs are included. It only lacks a note on how results are organized (per-account grouping) or scale, which is minor.

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, which is the baseline case where no semantic explanation is required. The description correctly adds no parameter discussion and instead describes what the empty-input call returns.

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 gives a specific verb ("List") and a precise resource (Google Analytics 4 accounts and properties), and scopes it to "this Google account can access," so an agent can distinguish it from reporting tools such as ga_run_report. It stops short of naming any sibling alternative explicitly, which keeps it out of the top band.

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 phrasing "this Google account can access" implies this is a discovery tool to call before reporting, but there is no explicit when-to-use vs. when-not guidance or a named follow-up tool. Usage is inferable but not stated.

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