Google Search Console MCP + Bing Webmaster Tools

List Search Console sitemaps

list_sitemaps

Read-onlyIdempotent

List sitemaps submitted to Google Search Console for a property, with last submitted and downloaded times, pending state, warnings, errors and submitted URL counts. Free.

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_sitemaps"
  }
}

Input Schema

Name	Required	Description	Default
`property`	No	Search Console property exactly as listed by list_search_console_properties, for example sc-domain:example.com or https://example.com/. Optional when the account has one property.

Output Schema

Name	Required	Description
`nextStep`	No	Optional suggestion for the user's next step. Mention it once when it helps; never open it or act on it automatically.
`property`	Yes
`sitemaps`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds that results carry pending state, warnings, errors and URL counts, but says nothing about behavior on an invalid or missing property, or the 'Free' qualifier's meaning.

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?

One front-loaded sentence covering purpose and returned fields, with zero filler. The trailing fragment 'Free.' is cryptic and slightly weakens an otherwise tight definition.

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?

Output schema exists, so return values need no elaboration, and the sole parameter is fully documented in the schema with annotations covering safety. Nothing an agent needs in order 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter with 100% schema description coverage that already explains the exact property format and that it is optional for single-property accounts. The description adds nothing beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List sitemaps submitted to Google Search Console for a property') plus the fields surfaced. The resource clearly separates it from list_search_console_properties and get_bing_* siblings, but the description never explicitly contrasts it with submit_sitemap or get_search_console_performance.

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?

Usage is only implied by 'for a property' and by the enumerated output fields (errors, warnings, pending state), which suggests auditing a property's sitemap health. There is no explicit when-to-use, when-not-to-use, or named alternative such as submit_sitemap for adding one.

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?