SEO GSC Wizard MCP

Show or hide properties on the dashboard

set_dashboard_visibility

Shows or hides registered properties on the GSC Wizard dashboard, the same switch as the app's Dashboard Management page. Visibility is also what makes a property usable by the other MCP tools, so use this to bring a newly added property into scope. Showing a property consumes a dashboard slot from the plan and is refused when the plan limit is reached; ClickHouse-synced properties are always shown and consume no slot. Hiding a property only removes it from the workspace: no data is deleted, and it can be shown again at any time. The response reports slot usage before and after.

Input Schema

Name	Required	Description	Default
`visible`	Yes	true = show on the dashboard (consumes a slot), false = hide.
`siteUrls`	Yes	Registered property URLs, as returned by list_sites.

Output Schema

Name	Required	Description	Default
`note`	No
`slots`	No
`updated`	No
`visible`	No
`unchanged`	No
`notRegistered`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026

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

changedOutput schema / properties / slots / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "limit": {
-        "$ref": "#/properties/slots/anyOf/0/properties/used"
-      },
-      "plan": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "used": {
-        "type": [
-          "number",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "limit": {
+        "$ref": "#/properties/slots/anyOf/0/properties/used"
+      },
+      "plan": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "used": {
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: showing consumes a dashboard slot and is refused at the plan limit, ClickHouse-synced properties are always shown and slot-free, hiding deletes no data and is reversible, and the response reports slot usage before/after. This is exactly the operational context an agent needs for a mutating toggle.

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 core action, then layered with the scope rationale, slot mechanics, and reversibility. Every sentence carries information, though it is on the denser end for a two-parameter toggle.

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 details are covered, and the description nonetheless previews that slot usage is reported. Scope, side effects, limits, and the sync exception are all present; nothing needed to call this correctly is missing.

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 100% (baseline 3), but the description still adds meaning: that the 'visible' flag maps to slot consumption and that siteUrls are registered property URLs from list_sites. This reinforces rather than merely repeats the schema.

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 (shows or hides) and resource (registered properties on the GSC Wizard dashboard), and anchors it to a known surface ('the same switch as the app's Dashboard Management page'). An agent can immediately tell this is a visibility toggle rather than a property-creation or site-management tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use it 'to bring a newly added property into scope,' and implies a when-not via the plan-limit refusal. It does not name an alternative tool, but with this large sibling set there is no obvious competing visibility tool, so the guidance is clear without exclusions.

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?