SEO GSC Wizard MCP

List tracked URLs

list_tracked_urls

Read-only

Use this when the user asks which of their tracked URLs are indexed or not, or wants the tracker's watchlist. Paginated list of URLs in the GSC Wizard Indexing Tracker for a property, newest-added first (createdAt, then id), with optional status filter and URL substring search. Filter options: all, indexed, not_indexed, pending, errors, warnings. Returns the current verdict / coverage / indexing state, last-crawl time, the Google-selected and user-declared canonicals, and the Search Console link per URL, all from the latest inspection. A canonical is null when Google did not report it or the URL has not been inspected yet. Not for counts only: use get_indexing_tracker; for one-off inspections use list_url_inspections.

Input Schema

Name	Required	Default
`page`	No
`filter`	No	all
`search`	No
`siteUrl`	Yes
`pageSize`	No

Output Schema

Name	Required	Description
`page`	No
`urls`	No
`total`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`message`	No
`siteUrl`	No
`nextStep`	No
`ordering`	No
`pageSize`	No
`sortedBy`	No
`sortOrder`	No
`thenOrder`	No
`configured`	No
`emptyBecause`	No
`methodLimits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

Added value: +{
+  "$ref": "#/properties/siteUrl",
+  "description": "Name of the top-level field that holds the rows sortedBy describes."
+}

Changed11 schema fields changedOct 18, 2026

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

addedOutput schema / properties / emptyBecause

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

addedOutput schema / properties / methodLimits

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

addedOutput schema / properties / nextStep

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

addedOutput schema / properties / ordering

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

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

changedOutput schema / properties / urls / items / additionalProperties
```
Previous value: -falseNew value: +true
```
addedOutput schema / properties / urls / items / properties / createdAt
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```

Changed5 schema fields changedOct 10, 2026
- addedOutput schema / properties / configured
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / message
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```
- addedOutput schema / properties / urls / items / properties / googleCanonical
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```
- addedOutput schema / properties / urls / items / properties / inspectionResultLink
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```
- addedOutput schema / properties / urls / items / properties / userCanonical
```
Added value: +{
+  "$ref": "#/properties/siteUrl"
+}
```
First observedOct 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already establish a safe read-only, closed-world operation, and the description adds substantial behavior: default ordering (createdAt, then id), pagination, the per-URL payload (verdict/coverage, last-crawl time, Google-selected and user-declared canonicals, Search Console link), and the null-canonical meaning when Google did not report it or the URL was never inspected.

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-loads the trigger sentence, then scope/ordering, then filter options, then return payload, then exclusions—a logical progression with little waste. The single long sentence enumerating returned fields is slightly dense but every clause is informative.

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?

Covers trigger, ordering, filtering, payload, null semantics, and sibling routing; an output schema exists so return details are a bonus, not a requirement. The only shortfall is that pagination parameters and the ambiguity of siteUrl (property vs. URL) are left to the schema.

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?

With 0% schema description coverage the description carries the burden: it enumerates the filter enum values and explains that search is a URL substring match, which is valuable. However, page, pageSize, and the required siteUrl (property identifier) get no explanation in the description, leaving the pagination contract only implicit in schema defaults.

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+resource (paginated list of tracked URLs in the GSC Wizard Indexing Tracker for a property) and names the exact question it answers (which tracked URLs are indexed). It is clearly distinguishable from get_indexing_tracker (counts) and list_url_inspections (one-off inspections) by name.

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 an explicit trigger ('when the user asks which of their tracked URLs are indexed or not, or wants the watchlist') and then names two exclusions with the alternatives to use instead: get_indexing_tracker for counts only and list_url_inspections for one-off inspections.

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?