SEO GSC Wizard MCP

List chart annotations

list_annotations

Read-only

Use this when the user asks which events or notes are marked on the chart, e.g. to explain a traffic change. Lists chart annotations visible to the user across scopes: platform-wide (Google ranking updates synced from the Search Status dashboard), account-wide (user notes), and property-scoped. Optionally restrict to one property. Property-scoped annotations are returned only when siteUrl is passed, and include every note on that property, whoever added it (the owner or a collaborator it is shared with), as on the GSC Wizard chart. Not for Google update rollout windows (begin and end): use list_algo_updates. Newest first (event_date descending), then by label.

Input Schema

Name	Required	Description
`endDate`	No	Optional filter: only include annotations on or before this date (YYYY-MM-DD). Omit to include all. Never pass null or "null".
`siteUrl`	No
`startDate`	No	Optional filter: only include annotations on or after this date (YYYY-MM-DD). Omit to include all. Never pass null or "null".

Output Schema

Name	Required	Description
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`nextStep`	No
`ordering`	No
`sortedBy`	No
`sortOrder`	No
`thenOrder`	No
`annotations`	No
`emptyBecause`	No
`methodLimits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 28, 2026

addedOutput schema / properties / listKey

Added value: +{
+  "description": "Name of the top-level field that holds the rows sortedBy describes.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / sortedBy / $ref
```
Added value: +"#/properties/listKey"
```
removedOutput schema / properties / sortedBy / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed21 schema fields changedOct 18, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
changedOutput schema / properties / annotations / items / additionalProperties
```
Previous value: -falseNew value: +true
```

changedOutput schema / properties / annotations / items / properties / category / $ref

Previous value: -"#/properties/annotations/items/properties/id"New value: +"#/properties/sortedBy"

changedOutput schema / properties / annotations / items / properties / color / $ref

Previous value: -"#/properties/annotations/items/properties/id"New value: +"#/properties/sortedBy"

changedOutput schema / properties / annotations / items / properties / description / $ref

Previous value: -"#/properties/annotations/items/properties/id"New value: +"#/properties/sortedBy"

changedOutput schema / properties / annotations / items / properties / event_date / $ref

Previous value: -"#/properties/annotations/items/properties/id"New value: +"#/properties/sortedBy"

changedOutput schema / properties / annotations / items / properties / external_id / $ref

Previous value: -"#/properties/annotations/items/properties/id"New value: +"#/properties/sortedBy"

changedOutput schema / properties / annotations / items / properties / external_source / $ref

Previous value: -"#/properties/annotations/items/properties/id"New value: +"#/properties/sortedBy"

addedOutput schema / properties / annotations / items / properties / id / $ref
```
Added value: +"#/properties/sortedBy"
```
removedOutput schema / properties / annotations / items / properties / id / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

changedOutput schema / properties / annotations / items / properties / label / $ref

Previous value: -"#/properties/annotations/items/properties/id"New value: +"#/properties/sortedBy"

changedOutput schema / properties / annotations / items / properties / scope / $ref

Previous value: -"#/properties/annotations/items/properties/id"New value: +"#/properties/sortedBy"

changedOutput schema / properties / annotations / items / properties / site_id / $ref

Previous value: -"#/properties/annotations/items/properties/id"New value: +"#/properties/sortedBy"

addedOutput schema / properties / emptyBecause

Added value: +{
+  "$ref": "#/properties/sortedBy"
+}

addedOutput schema / properties / methodLimits

Added value: +{
+  "$ref": "#/properties/sortedBy"
+}

addedOutput schema / properties / nextStep

Added value: +{
+  "$ref": "#/properties/sortedBy"
+}

addedOutput schema / properties / ordering

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "sortOrder": {
+            "$ref": "#/properties/sortedBy"
+          },
+          "sortedBy": {
+            "$ref": "#/properties/sortedBy"
+          },
+          "thenBy": {
+            "$ref": "#/properties/sortedBy"
+          },
+          "thenOrder": {
+            "$ref": "#/properties/sortedBy"
+          }
+        },
+        "type": "object"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / sortOrder

Added value: +{
+  "$ref": "#/properties/sortedBy"
+}

addedOutput schema / properties / sortedBy

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / thenBy

Added value: +{
+  "$ref": "#/properties/sortedBy"
+}

addedOutput schema / properties / thenOrder

Added value: +{
+  "$ref": "#/properties/sortedBy"
+}

First observedOct 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, and the description adds non-obvious behavior well beyond that: property-scoped notes only appear when siteUrl is passed, they include notes added by collaborators regardless of author, and results are sorted by event_date descending then label. That is exactly the kind of scoping and ordering detail an agent cannot infer from annotations.

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 trigger and free of filler; each sentence adds a distinct fact (scope, siteUrl gating, author visibility, exclusion, sort order). It is one dense run-on paragraph, so the sort-order and GSC Wizard asides slightly crowd the core routing signal, but nothing is genuinely 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?

An output schema exists, so return-shape explanation is unnecessary, and the description still covers scope semantics, the gating parameter, visibility rules, and ordering. For a 3-param, zero-required read tool, an agent has everything needed to select and call it correctly.

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 coverage is 67%, with startDate/endDate already documented in the schema; the description compensates for the undocumented siteUrl by explaining that it is what unlocks property-scoped annotations and that omitting it changes the result set entirely. It does not restate the date filter semantics, but the schema handles those, so the gap is minor rather than material.

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 ('Lists chart annotations visible to the user') and immediately enumerates the scopes covered (platform-wide, account-wide, property-scoped). The closing sentence explicitly distinguishes it from list_algo_updates, so an agent can route without opening either schema.

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?

Opens with the trigger condition ('Use this when the user asks which events or notes are marked on the chart, e.g. to explain a traffic change') and gives an explicit exclusion plus the correct alternative ('Not for Google update rollout windows... use list_algo_updates'). Both when-to-use and when-not are covered.

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

All SEO GSC Wizard MCP tools Inspect

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

Need Help?