Google Search Console MCP + Bing Webmaster Tools

List Search Console and Bing sites

list_search_console_properties

Read-onlyIdempotent

List Search Console properties connected to this account and the sites in Bing Webmaster Tools, with links to connect either one. Use the returned property names in the other tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_search_console_properties"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`bing`	Yes
`google`	Yes
`connect`	Yes
`message`	No	What to tell the user when nothing is connected yet.
`nextStep`	No	Optional suggestion for the user's next step. Mention it once when it helps; never open it or act on it automatically.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

addedOutput schema / properties / message

Added value: +{
+  "description": "What to tell the user when nothing is connected yet.",
+  "type": "string"
+}

Changed1 schema field changedOct 29, 2026

addedOutput schema / properties / nextStep

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional suggestion for the user's next step. Mention it once when it helps; never open it or act on it automatically.",
+  "properties": {
+    "label": {
+      "description": "Short suggestion to show the user.",
+      "type": "string"
+    },
+    "url": {
+      "description": "Page in the user's CrakSEO account.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "label",
+    "url"
+  ],
+  "type": "object"
+}

First observedOct 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful context beyond them: results span two separate providers and include connect links for either, hinting that unconnected services may appear. It doesn't mention auth requirements or behavior when nothing is connected.

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?

Two sentences, both front-loaded with the resource then the follow-up action. Nothing is redundant with the name or title.

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 need not be spelled out, and with zero parameters the surface area is small. The description covers what is listed and what to do with the results; only the empty/unconnected-account case is left unstated.

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?

Zero parameters, so the schema baseline applies and the description has nothing to disambiguate. Credit for not padding with irrelevant argument talk.

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 (List) and two specific resources (Search Console properties, Bing Webmaster Tools sites), plus a secondary output (connect links). No sibling tool does discovery of connected properties, so an agent can distinguish it from get_search_console_performance or get_bing_webmaster_stats 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 Guidelines4/5

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

Explicitly says to use the returned property names in the other tools, which positions this as the prerequisite/discovery call in the workflow. It doesn't state exclusions or when not to call it, but the sequencing guidance is clear enough to act on.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Google Search Console MCP + Bing Webmaster Tools 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?