OnPage.dev

Explain Google and Bing

explain_google

Read-onlyIdempotent

Explain what Google Search Console and Bing Webmaster Tools report, and what to do. Pick with mode: index_status = Index coverage and rich result statuses, with the fix. Needs rows[{url, coverageState, verdict, indexingState, robotsTxtState, pageFetchState}]. manual_action = A manual action, with the cleanup plan and reconsideration draft. Needs action. bing = Bing Webmaster crawl issues, and Bing against Google per query.

Input Schema

Name	Required	Description
`mode`	No	Default index_status.
`rows`	No
`site`	No	The site or Search Console property.
`action`	No	The manual action as Search Console shows it.
`detail`	No	brief = short summary.
`issues`	No	Bing crawl or index issues.
`memory_key`	No	site_memory key, records this call.
`sample_urls`	No	Example URLs Google listed.
`bing_queries`	No
`google_queries`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

removedOutput schema / description

Removed value: -"The result as structured data; fields depend on mode."

Changed2 schema fields changedOct 13, 2026

changedInput schema / properties / detail / description

Previous value: -"brief returns a short summary, default full."New value: +"brief = short summary."

changedInput schema / properties / memory_key / description

Previous value: -"Optional site_memory key, to record this call in the site memory."New value: +"site_memory key, records this call."

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / detail

Added value: +{
+  "description": "brief returns a short summary, default full.",
+  "enum": [
+    "full",
+    "brief"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / memory_key

Added value: +{
+  "description": "Optional site_memory key, to record this call in the site memory.",
+  "maxLength": 80,
+  "type": "string"
+}

Changed4 schema fields changedOct 12, 2026

addedInput schema / properties / bing_queries

Added value: +{
+  "items": {
+    "properties": {
+      "clicks": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "impressions": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "position": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "query": {
+        "maxLength": 2000,
+        "type": "string"
+      }
+    },
+    "required": [
+      "query",
+      "clicks"
+    ],
+    "type": "object"
+  },
+  "maxItems": 5000,
+  "type": "array"
+}

addedInput schema / properties / google_queries

Added value: +{
+  "items": {
+    "properties": {
+      "clicks": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "impressions": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "position": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "query": {
+        "maxLength": 2000,
+        "type": "string"
+      }
+    },
+    "required": [
+      "query",
+      "clicks"
+    ],
+    "type": "object"
+  },
+  "maxItems": 5000,
+  "type": "array"
+}

addedInput schema / properties / issues

Added value: +{
+  "description": "Bing crawl or index issues.",
+  "items": {
+    "properties": {
+      "issue": {
+        "maxLength": 200,
+        "type": "string"
+      },
+      "url": {
+        "maxLength": 2048,
+        "type": "string"
+      }
+    },
+    "required": [
+      "url",
+      "issue"
+    ],
+    "type": "object"
+  },
+  "maxItems": 5000,
+  "type": "array"
+}

changedInput schema / properties / mode / enum

Previous value: -[
-  "index_status",
-  "manual_action"
-]New value: +[
+  "index_status",
+  "manual_action",
+  "bing"
+]

AddedOct 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds genuine non-structured context: it returns remediation content ('with the fix', 'the cleanup plan and reconsideration draft') rather than raw report data, which an agent could not infer from the 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?

Front-loads the purpose, then uses a compact mode = meaning / needs-X pattern that is easy to scan. Dense but every clause carries information; the trailing 'bing' clause is slightly terse about what data it consumes but not wasteful.

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?

For a 10-parameter, multi-mode tool with an output schema present, the description covers all three modes and their required inputs, and the return shape is handled by the output schema. Minor gaps remain (site, detail, memory_key are left to the schema), but nothing critical for correct invocation is missing.

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?

Schema description coverage is 70%, and the description adds mode-conditional parameter requirements that the schema does not encode since all 10 params are optional: rows[{url, coverageState, verdict, indexingState, robotsTxtState, pageFetchState}] for index_status, action for manual_action. This is real added meaning over the flat optional schema.

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 ('Explain what Google Search Console and Bing Webmaster Tools report, and what to do') and breaks the tool into three named modes with their outputs. An agent can distinguish it from diagnostic siblings like site_audit or technical, though no sibling is named explicitly.

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?

Gives a clear mode-selection rule (index_status / manual_action / bing) and states the input each mode needs (rows[...], action, bing query data), which is effectively the when-to-use guidance. It does not state when to prefer a sibling tool or when this tool is inappropriate.

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

All OnPage.dev tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.