Skip to main content
Glama
Sign In
Google Analytics MCP Server

Google Analytics MCP Server

Official
by googleanalytics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_property_annotations

Read-only

Retrieve annotations for a Google Analytics property to review notes on specific dates or periods, such as campaign launches, service releases, or traffic changes.

Instructions

Returns annotations for a property.

Annotations are a feature that allows you to leave notes on Google Analytics for specific dates or periods. They are typically used to record service releases, marketing campaign launches or changes, and rapid traffic increases or decreases due to external factors.

Args: property_id: The Google Analytics property ID. Accepted formats are: - A number - A string consisting of 'properties/' followed by a number

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": {
      "property_id": "<property_id>"
    },
    "name": "list_property_annotations"
  }
}

Input Schema

NameRequiredDescriptionDefault
property_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0
  2. Removedv0.5.0
  3. Changed3 schema fields changedv0.3.0
    • removedInput schema / properties / property_id / title
      Removed value: -"Property Id"
    • removedInput schema / title
      Removed value: -"list_property_annotationsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "list_property_annotationsOutput",
-  "type": "object"
-}New value: +null
  4. Addedv1.0.0

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, openWorldHint=true, so the safety profile is covered. The description adds domain context about annotation semantics but says nothing about pagination, result volume, or ordering, which matters for a list endpoint.

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?

Purpose is front-loaded in the first sentence, followed by useful domain context and a well-formatted args block. The middle paragraph is somewhat expendable for an agent but justifies its place by clarifying what data comes back conceptually.

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 one-parameter read tool with no output schema, the description covers the input well but leaves the return value opaque (fields per annotation, pagination behavior). It is adequate rather than complete.

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?

Schema description coverage is 0%, so the description carries the full burden, and it delivers by spelling out the accepted property_id formats (bare number or 'properties/N'). It is not exhaustive about validation edge cases but covers the practical forms.

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 (Returns) and resource (annotations for a property), which is unambiguous on its own. It does not differentiate from siblings, though no sibling appears to overlap on annotations, so the risk is low.

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 explanation of what annotations are (notes on dates/periods for releases, campaigns, traffic anomalies) implicitly conveys when the tool is relevant, but there is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named.

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

Deploy Server

Other Tools