SEO GSC Wizard MCP

Get account info

get_account_info

Read-only

Use this when the user asks which Google accounts, scopes or plan their GSC Wizard login has. Returns the authenticated user, the connected Google accounts (email + scopes), and the subscription status. Useful as a first call to confirm the MCP server is wired up correctly and the user has the data sources you expect. Not for the property list: use list_sites. googleAccounts are oldest first (connectedAt ascending); the first is isPrimary, the default account.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`user`	No
`access`	No
`apiKey`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`warning`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`sortOrder`	No
`thenOrder`	No
`emptyBecause`	No
`methodLimits`	No
`subscription`	No
`googleAccounts`	No
`profileUnavailable`	No
`subscriptionUnavailable`	No
`googleAccountsUnavailable`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

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

Changed18 schema fields changedOct 18, 2026

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

addedOutput schema / properties / emptyBecause

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

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

addedOutput schema / properties / googleAccountsUnavailable

Added value: +{
+  "$ref": "#/properties/googleAccounts/items/properties/isPrimary"
+}

addedOutput schema / properties / methodLimits

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

addedOutput schema / properties / nextStep

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

addedOutput schema / properties / ordering

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

addedOutput schema / properties / profileUnavailable

Added value: +{
+  "$ref": "#/properties/googleAccounts/items/properties/isPrimary"
+}

addedOutput schema / properties / sortOrder

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

addedOutput schema / properties / sortedBy

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

changedOutput schema / properties / subscription / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "cancelAtPeriodEnd": {
-        "$ref": "#/properties/googleAccounts/items/properties/isPrimary"
-      },
-      "currentPeriodEnd": {
-        "$ref": "#/properties/user/properties/id"
-      },
-      "plan": {
-        "$ref": "#/properties/user/properties/id"
-      },
-      "status": {
-        "$ref": "#/properties/user/properties/id"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "cancelAtPeriodEnd": {
+        "$ref": "#/properties/googleAccounts/items/properties/isPrimary"
+      },
+      "currentPeriodEnd": {
+        "$ref": "#/properties/user/properties/id"
+      },
+      "plan": {
+        "$ref": "#/properties/user/properties/id"
+      },
+      "status": {
+        "$ref": "#/properties/user/properties/id"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / subscriptionUnavailable

Added value: +{
+  "$ref": "#/properties/googleAccounts/items/properties/isPrimary"
+}

addedOutput schema / properties / thenBy

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

addedOutput schema / properties / thenOrder

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

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

addedOutput schema / properties / warning

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

First observedOct 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the description adds value with non-obvious behavior: the googleAccounts ordering (connectedAt ascending) and that the first entry is the primary/default account. It stops short of stating failure modes, such as what is returned when no Google account is connected or a token has expired.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger condition, followed by the payload, a diagnostic use case, and the sibling exclusion, then the ordering caveat. Every sentence carries distinct information; nothing restates the title or annotations.

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 needn't be spelled out, yet the description still names the three returned components and their ordering. For a zero-parameter, read-only info tool this covers everything an agent needs to select and call it.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline is 4. The return-ordering note is the closest thing to a semantic hint and is already covered above.

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 (get/returns) plus the exact payload: authenticated user, connected Google accounts with email + scopes, and subscription status. It also explicitly separates itself from list_sites, so the agent can distinguish it from the property-listing siblings 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 both triggers ('when the user asks which Google accounts, scopes or plan') and a second diagnostic use case ('first call to confirm the MCP server is wired up'). It also names the exclusion and the correct alternative: 'Not for the property list: use list_sites.'

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?