Google Analytics MCP Server

Get Analytics Metadata

get_metadata

Retrieve available dimensions and metrics for a Google Analytics property. Specify property ID and optionally filter by type for metadata discovery.

Instructions

Get available dimensions and metrics for Google Analytics property

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": {
      "propertyId": "<propertyId>"
    },
    "name": "get_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`propertyId`	Yes	Google Analytics property ID (e.g., 123456789). Required for all queries.
`type`	No	Type of metadata to retrieve	both

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.5Jun 18, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description alone must disclose behavioral traits. It fails to mention that the tool is read-only or any permissions needed, leaving the agent without assurance of side effects.

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 a single concise sentence with no wasted words, front-loaded with the key action and resource.

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?

For a simple retrieval tool with two parameters, the description is adequate but not complete. It does not indicate the return format or mention that no output schema exists, which could help the agent plan subsequent steps.

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 100%, so the schema already explains both parameters. The description adds no additional meaning beyond what the schema provides, meeting the baseline.

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?

The description 'Get available dimensions and metrics for Google Analytics property' clearly states the verb ('Get') and the resource ('available dimensions and metrics'), which is specific and distinguishes it from sibling tools like 'realtime_data' and 'analytics_report'.

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 description does not provide explicit guidance on when to use this tool versus alternatives, such as 'search_metadata'. The purpose is implied but no 'when not to use' or context is given.

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

Deploy Server