SEO GSC Wizard MCP

List shareable reports

list_shared_reports

Read-only

Use this when the user asks which reports they have saved or shared, and with whom. Lists the shareable reports saved on the account, newest first (createdAt descending), each with its view URL and the clients currently granted access (sharedWith, oldest grant first). A sharedWith entry with pendingConfirmation true is a grant waiting for the account owner to confirm it from their email: that client cannot open the report yet. Use it to find a reportId before calling manage_report_access or delete_shared_report, or to audit who can see which report. Not for the client contacts themselves: use list_report_clients.

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description
`count`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`reports`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`sortOrder`	No
`thenOrder`	No
`emptyBecause`	No
`methodLimits`	No
`unsharedCount`	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"
-]
```

Changed1 schema field changedOct 24, 2026
- addedOutput schema / properties / reports / items / properties / sharedWith / items / properties / pendingConfirmation
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```

Changed22 schema fields changedOct 18, 2026

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

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"
+    }
+  ]
+}

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

changedOutput schema / properties / reports / items / properties / createdAt / $ref

Previous value: -"#/properties/reports/items/properties/reportId"New value: +"#/properties/sortedBy"

changedOutput schema / properties / reports / items / properties / dataSourceType / $ref

Previous value: -"#/properties/reports/items/properties/reportId"New value: +"#/properties/sortedBy"

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

changedOutput schema / properties / reports / items / properties / reportType / $ref

Previous value: -"#/properties/reports/items/properties/reportId"New value: +"#/properties/sortedBy"

changedOutput schema / properties / reports / items / properties / sharedWith / items / additionalProperties
```
Previous value: -falseNew value: +true
```
changedOutput schema / properties / reports / items / properties / sharedWith / items / properties / clientId / $ref
```
Previous value: -"#/properties/reports/items/properties/reportId"New value: +"#/properties/sortedBy"
```
changedOutput schema / properties / reports / items / properties / sharedWith / items / properties / email / $ref
```
Previous value: -"#/properties/reports/items/properties/reportId"New value: +"#/properties/sortedBy"
```
changedOutput schema / properties / reports / items / properties / sharedWith / items / properties / grantedAt / $ref
```
Previous value: -"#/properties/reports/items/properties/reportId"New value: +"#/properties/sortedBy"
```
changedOutput schema / properties / reports / items / properties / sharedWith / items / properties / name / $ref
```
Previous value: -"#/properties/reports/items/properties/reportId"New value: +"#/properties/sortedBy"
```

changedOutput schema / properties / reports / items / properties / title / $ref

Previous value: -"#/properties/reports/items/properties/reportId"New value: +"#/properties/sortedBy"

changedOutput schema / properties / reports / items / properties / url / $ref

Previous value: -"#/properties/reports/items/properties/reportId"New value: +"#/properties/sortedBy"

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.5/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive), and the description adds substantial semantics beyond them: newest-first ordering by createdAt, sharedWith returned oldest-grant-first, and the meaning of pendingConfirmation true (the client cannot open the report until the owner confirms from email). That last point is behavior an agent could not infer from any structured field.

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?

Four short sentences, front-loaded with the trigger and output shape, with the exclusion last. Each sentence carries information, though the two inline parentheticals (createdAt descending, oldest grant first) make it denser than needed.

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?

Return-value semantics are spelled out even though an output schema exists, and ordering, access-audit use, and sibling routing are all covered. The only real hole is result-size behavior for the limit parameter, which matters for an auditing use case.

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 coverage is 0% for the single `limit` parameter, and the description never mentions it — no indication that results are capped (default 50, max 100) or that there is no pagination cursor. The name and bounds make the parameter guessable, but the description leaves an agent unable to tell whether a truncated result means 'that is all' or 'there is more'.

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 the shareable reports saved on the account') with scope and ordering, and explicitly separates itself from the semantically adjacent list_report_clients. An agent can distinguish it from create_shared_report and delete_shared_report without opening a 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?

Gives a concrete trigger ('when the user asks which reports they have saved or shared, and with whom'), two downstream uses (finding a reportId for manage_report_access or delete_shared_report, auditing access), and an explicit exclusion with the alternative ('Not for the client contacts themselves: use list_report_clients').

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?