Google Search Console MCP + Bing Webmaster Tools

Google Search Console performance

get_search_console_performance

Read-onlyIdempotent

Google Search Console performance: clicks, impressions, CTR and average position by query, page or date for a date range, with optional query or page filters. Data lags about two days. 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": "get_search_console_performance"
  }
}

Input Schema

Name	Required	Description
`endDate`	No	Last day, YYYY-MM-DD. Default two days ago.
`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.
`rowLimit`	No	Most rows to return, 1 to 1000. Default 100.
`startDate`	No	First day, YYYY-MM-DD. Default 28 days before endDate.
`dimensions`	No	How to group rows: query, page and/or date. Default query.
`pageContains`	No	Only rows whose page URL contains this text.
`queryContains`	No	Only rows whose query contains this text.

Output Schema

Name	Required	Description
`rows`	Yes
`totals`	Yes
`endDate`	Yes
`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
`startDate`	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.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the bar is lower. The description still adds real context beyond them: a ~2-day data lag (freshness expectation) and 'Free' (no billing/quota cost concern), which an agent would otherwise not know.

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 carries the purpose, dimensions and filters, followed by two short facts on lag and cost. Dense and near-waste-free, with only the fragment 'Free.' being slightly clipped rather than a full sentence.

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?

Output schema exists so return values need no explanation, and 7 optional params with full schema descriptions are covered. The lag note closes the main behavioral gap; the only missing piece is explicit routing to list_search_console_properties for the property argument, which the schema does mention.

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 coverage is 100%, so every parameter including defaults, date patterns and row limits is already documented. The description only restates that grouping is by query, page or date and that query/page filters exist, adding no syntax or semantics beyond the schema — baseline 3.

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+resource (retrieves Google Search Console performance) and enumerates the four returned metrics plus the grouping dimensions and filters. It is clearly distinct from the Bing siblings by naming Google Search Console, though it never explicitly contrasts itself with get_bing_webmaster_stats.

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 context is implied by the metrics and filter list, and the two-day lag steers timing expectations, but there is no explicit statement of when to prefer this over get_bing_webmaster_stats or that list_search_console_properties should be called first to obtain a valid property value.

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?