SEO GSC Wizard MCP

List report clients

list_report_clients

Read-only

Use this when the user asks who their report clients are, or needs a clientId to share a report. Lists the client contacts on the account: the people who can be granted access to a shareable report. A client is just an email address (plus an optional name); they sign in with it to view reports shared with them. Use this to find a clientId for manage_report_access, or create_report_client to add a new contact. Not for which reports each client can see: use list_shared_reports. Newest first (createdAt descending).

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description
`count`	No
`thenBy`	No
`clients`	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
`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"
-]
```

Changed15 schema fields changedOct 18, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
changedOutput schema / properties / clients / items / additionalProperties
```
Previous value: -falseNew value: +true
```
addedOutput schema / properties / clients / items / properties / clientId / $ref
```
Added value: +"#/properties/sortedBy"
```
removedOutput schema / properties / clients / items / properties / clientId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

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

Previous value: -"#/properties/clients/items/properties/clientId"New value: +"#/properties/sortedBy"

changedOutput schema / properties / clients / items / properties / email / $ref

Previous value: -"#/properties/clients/items/properties/clientId"New value: +"#/properties/sortedBy"

changedOutput schema / properties / clients / items / properties / name / $ref

Previous value: -"#/properties/clients/items/properties/clientId"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.3/5.0

Behavior4/5

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

Annotations already cover read-only, closed-world, non-destructive behavior, so the description correctly spends its space on domain semantics instead: clients are email identities that sign in to view shared reports, and results come newest first by createdAt. It does not discuss pagination behavior or result caps for an account with many clients.

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 the core definition, then routing, then ordering — a sensible progression. Slightly dense with four sentences, and the 'they sign in with it to view reports shared with them' clause is helpful context rather than wasted space.

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?

An output schema exists and annotations carry the safety profile, so the description need not explain return values — and it doesn't try. The one real omission is the `limit` parameter and what happens past the default page size, which matters for accounts with many clients.

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 note that it defaults to 100 or caps at 500, or how to page beyond that. It does add useful semantics about ordering ('createdAt descending'), which the schema does not express, keeping this at baseline rather than lower.

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 concrete verb and resource ('Lists the client contacts on the account') and defines what a client is (an email address plus optional name). The distinction from create_report_client, manage_report_access, and list_shared_reports is unmistakable.

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 ('when the user asks who their report clients are, or needs a clientId to share a report') and names both downstream consumers of the returned clientId. It also states an explicit exclusion: not for which reports each client sees, use list_shared_reports.

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?