SEO GSC Wizard MCP

List Bing Webmaster sites

list_bing_sites

Read-only

Use this when the user asks which sites their Bing Webmaster Tools account holds, or before any other get_bing_* tool, to find the exact site URL Bing recognises. Lists the sites in the Bing Webmaster Tools account linked to GSC Wizard (via the stored Bing Webmaster API key), sorted alphabetically; siteDetails gives each one with isVerified, and Bing serves data only for a verified site. Not for Google Search Console properties: use list_sites. Returns notConfigured: true when no Bing Webmaster API key is set up in the GSC Wizard app.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`hint`	No
`count`	No
`sites`	No
`thenBy`	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
`dataSource`	No
`siteDetails`	No
`emptyBecause`	No
`methodLimits`	No
`notConfigured`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

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

Changed15 schema fields changedOct 18, 2026

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

changedOutput schema / properties / dataSource / $ref

Previous value: -"#/properties/hint"New value: +"#/properties/siteDetails/items/properties/url"

addedOutput schema / properties / emptyBecause

Added value: +{
+  "$ref": "#/properties/siteDetails/items/properties/url"
+}

addedOutput schema / properties / hint / $ref

Added value: +"#/properties/siteDetails/items/properties/url"

removedOutput schema / properties / hint / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / methodLimits

Added value: +{
+  "$ref": "#/properties/siteDetails/items/properties/url"
+}

addedOutput schema / properties / nextStep

Added value: +{
+  "$ref": "#/properties/siteDetails/items/properties/url"
+}

addedOutput schema / properties / notConfigured / $ref

Added value: +"#/properties/siteDetails/items/properties/isVerified"

removedOutput schema / properties / notConfigured / type
```
Removed value: -[
-  "boolean",
-  "null"
-]
```

addedOutput schema / properties / ordering

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

addedOutput schema / properties / siteDetails

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "isVerified": {
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "url": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / sortOrder

Added value: +{
+  "$ref": "#/properties/siteDetails/items/properties/url"
+}

addedOutput schema / properties / sortedBy

Added value: +{
+  "$ref": "#/properties/siteDetails/items/properties/url"
+}

addedOutput schema / properties / thenBy

Added value: +{
+  "$ref": "#/properties/siteDetails/items/properties/url"
+}

addedOutput schema / properties / thenOrder

Added value: +{
+  "$ref": "#/properties/siteDetails/items/properties/url"
+}

First observedOct 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnly/openWorld/non-destructive), yet the description adds substantial context beyond them: which credential backs the account (stored Bing Webmaster API key via GSC Wizard), alphabetical ordering, that siteDetails carries isVerified, that Bing serves data only for verified sites, and the notConfigured: true failure mode when no key is configured.

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 when-to-use condition and the sibling exclusion, and every clause carries information. It is dense and slightly run-on through semicolons, which costs a point on readability but nothing is wasted.

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?

For a zero-param read tool with an output schema, this covers everything an agent needs: trigger conditions, ordering, key field (isVerified), the verification prerequisite, and the notConfigured response case.

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 zero parameters, so the baseline is 4; there is no parameter semantics to clarify and the description correctly does not invent any.

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 (list the sites in the Bing Webmaster Tools account) and immediately differentiates itself from the similarly named list_sites, which is for GSC properties. An agent can select between the two without opening either 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 explicit positive triggers (user asks which sites the account holds) plus a sequencing rule ('before any other get_bing_* tool, to find the exact site URL Bing recognises') and an explicit exclusion with the named alternative for GSC properties.

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?