Skip to main content
Glama

Visibility Genies

Read measurement health

get_google_analytics_measurement_health
Read-only

Checks how the connected Google Analytics property is set up: web streams, key events, custom definitions and any configuration issues. 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_measurement_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
errorNo
issuesNo
sourceNo
statusYes
summaryNo
keyEventsNo
webStreamsNo
otherStreamsNo
customDefinitionsNo

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 the description's "Read only and free" is largely redundant, though "free" does add a cost signal not present in the annotations. It usefully scopes what is inspected (streams, key events, custom definitions, config issues) but says nothing about what happens when no property is connected or how issues are classified. The output schema carries the return-shape burden.

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 short sentences with the purpose and the inspected scope front-loaded, and no filler. The trailing "Read only and free" is slightly redundant with annotations but is brief enough not to hurt the flow.

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 single-parameter read tool with an output schema and full annotation coverage, the description supplies everything needed to call it: what it inspects and that it is a safe read. Only the timing relative to the GA reporting siblings is left implicit.

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?

Only one parameter (projectId) and schema description coverage is 100%, with the schema itself explaining the billing context and pointing to list_projects. The description adds no parameter meaning beyond that, which is acceptable given the schema does the work, so the 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 ("Checks how the connected Google Analytics property is set up") and enumerates exactly what is inspected: web streams, key events, custom definitions, configuration issues. This is clearly a configuration-diagnostic tool, distinct in kind from the sibling report tools (overview, breakdown, performance), though it never names an alternative to confirm that distinction.

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?

Usage is only implied: an agent can infer this is the tool to call when validating that a GA property is instrumented before trusting other GA numbers. There is no explicit when-to-use, no prerequisite (e.g., a connected GA property must exist), and no stated relationship to the reporting siblings. The "free" note hints it is cheap to call but does not constitute guidance.

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