Skip to main content
Glama
Sign In

SEO GSC Wizard MCP

by com.gscwizard.mcp
OverviewDiscussionsAdmin

Create a shareable report

create_shared_report

Saves a table of rows as a shareable GSC Wizard report. Pass the rows you got from another tool (e.g. query_top_queries, get_content_group_performance) plus the columns describing which fields to show; the report renders at view time, so the stored payload stays small. THIS IS STEP 1 OF 3: the returned URL opens for NOBODY until access is granted, not even for the account owner, because the viewer is the client portal and requires a client login. To actually share it: (2) create_report_client with the recipient's email, then (3) manage_report_access to grant them the report. A recipient never shared with before also needs the account owner to confirm the share from the email GSC Wizard sends them. Do not hand the URL to anyone before access is granted; it will not open. Up to 50 reports per account; delete old ones with delete_shared_report.

Input Schema

NameRequiredDescriptionDefault
rowsYesThe table rows. Each row is an object keyed by the column `key` values.
titleYes
columnsYesColumn definitions, in display order.
siteUrlNoProperty this report is about; recorded on the report for context.
dateRangeNoReporting period, shown in the report header.
reportTypeNoFree-form label for what produced the report (e.g. "top-queries").mcp
dataSourceTypeNoWhich kind of report this is, for the viewer.inline
comparisonRangeNoComparison period, shown alongside the reporting period.

Output Schema

NameRequiredDescriptionDefault
noteNo
reportNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • changedOutput schema / properties / report / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "createdAt": {
-        "$ref": "#/properties/report/anyOf/0/properties/reportId"
-      },
-      "dataSourceType": {
-        "$ref": "#/properties/report/anyOf/0/properties/reportId"
-      },
-      "reportId": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "reportType": {
-        "$ref": "#/properties/report/anyOf/0/properties/reportId"
-      },
-      "rowCount": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "siteUrl": {
-        "$ref": "#/properties/report/anyOf/0/properties/reportId"
-      },
-      "title": {
-        "$ref": "#/properties/report/anyOf/0/properties/reportId"
-      },
-      "url": {
-        "$ref": "#/properties/report/anyOf/0/properties/reportId"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "createdAt": {
+        "$ref": "#/properties/report/anyOf/0/properties/reportId"
+      },
+      "dataSourceType": {
+        "$ref": "#/properties/report/anyOf/0/properties/reportId"
+      },
+      "reportId": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "reportType": {
+        "$ref": "#/properties/report/anyOf/0/properties/reportId"
+      },
+      "rowCount": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "siteUrl": {
+        "$ref": "#/properties/report/anyOf/0/properties/reportId"
+      },
+      "title": {
+        "$ref": "#/properties/report/anyOf/0/properties/reportId"
+      },
+      "url": {
+        "$ref": "#/properties/report/anyOf/0/properties/reportId"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / dataSourceType / enum
      Previous value: -[
-  "inline",
-  "queries",
-  "pages",
-  "countries",
-  "rankings",
-  "content-group",
-  "page-performance"
-]New value: +[
+  "inline",
+  "queries",
+  "pages",
+  "countries",
+  "rankings",
+  "content-group",
+  "page-performance",
+  "migration"
+]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses the non-obvious failure mode: the returned URL opens for nobody until access is granted, because the viewer is the client portal. It also states the 50-reports-per-account quota, the delete_shared_report cleanup path, and the view-time rendering that keeps the stored payload small.

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 action and payload shape, then the critical three-step warning. The closing 'Do not hand the URL to anyone before access is granted; it will not open' restates the earlier warning almost verbatim and could be trimmed without losing information.

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 values need not be spelled out, and the description still explains that the return includes a URL. For an 8-param, nested-schema write tool, the description covers the sequencing and access prerequisites that an agent could not infer from the schema alone.

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 88%, so the structured schema already carries most parameter meaning. The description adds real linkage semantics — that `rows` should come from another tool's output and `columns` selects which fields render — which clarifies how the two required arrays relate to each other. It does not touch the optional metadata params (siteUrl, dateRange, dataSourceType), which is acceptable given the schema documents them.

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 ('Saves a table of rows as a shareable GSC Wizard report') and implicitly separates itself from list_shared_reports, delete_shared_report, and manage_report_access. An agent knows immediately this creates the artifact rather than listing or granting it.

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 an explicit prerequisite (rows from query_top_queries or get_content_group_performance), names the exact follow-up tools (create_report_client, then manage_report_access), and warns what happens if the order is skipped. Also flags the account-owner email confirmation requirement for first-time recipients.

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 toolsInspect
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