SEO GSC Wizard MCP

Create a content group

create_content_group

Creates a content group partition on a property. Rules are an array of { type, value } objects (prefix / contains / regex / equals) that match URLs into the group. Group names are unique per site. A regex rule that cannot compile is rejected; one that is valid but unsupported by the warehouse (a lookahead, lookbehind or backreference) or skipped as ReDoS-prone is accepted and reported in ruleWarnings. Relay those to the user, since a skipped pattern matches no pages at all.

Input Schema

Name	Required	Description	Default
`name`	Yes
`color`	No
`rules`	Yes
`siteUrl`	Yes
`description`	No

Output Schema

Name	Required	Description	Default
`group`	No
`ruleWarnings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 18, 2026

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

changedOutput schema / properties / group / properties / rules / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "type": {
-          "$ref": "#/properties/group/properties/id"
-        },
-        "value": {
-          "$ref": "#/properties/group/properties/id"
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "type": {
+          "$ref": "#/properties/group/properties/id"
+        },
+        "value": {
+          "$ref": "#/properties/group/properties/id"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / ruleWarnings

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "$ref": "#/properties/group/properties/id"
+      },
+      "message": {
+        "$ref": "#/properties/group/properties/id"
+      },
+      "pattern": {
+        "$ref": "#/properties/group/properties/id"
+      },
+      "severity": {
+        "$ref": "#/properties/group/properties/id"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false). The description goes well beyond by disclosing that group names are unique per site, that non-compiling regex is rejected, that valid-but-unsupported or ReDoS-skipped patterns are silently accepted as no-match, and that this is surfaced via `ruleWarnings`. That is exactly the behavioral context an agent needs and cannot get from annotations.

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 sentences, front-loaded with purpose before drill-down into rules and validation behavior. The final regex caveat is longer than average but is high-value operational detail rather than padding; nothing reads as filler.

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 so return values needn't be covered, and the description still flags `ruleWarnings` for the agent. Combined with the regex semantics and uniqueness constraint, this is nearly complete for a create tool; only the remaining input parameters (siteUrl, color, description) are unaddressed.

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 description coverage is 0%, so the description carries the full parameter burden, and it does well on `rules` – explaining the { type, value } shape, the four match types, and regex edge cases – plus the name-uniqueness constraint. However, siteUrl, color, and description are never addressed, leaving half the parameters documented only by their bare JSON types.

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?

Opens with a specific verb+resource ("Creates a content group partition on a property") and immediately scopes what a group is. The verb 'Creates' cleanly distinguishes it from the sibling update_content_group, delete_content_group, and list_content_groups without needing to name them.

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

Usage Guidelines3/5

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

The description implies usage through the rules-matching explanation, but never states when to reach for this tool versus update_content_group or when a content group is the right construct. No explicit when/when-not guidance or named alternatives; usage must be inferred.

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?