Skip to main content
Glama
saurabhsharma2u

Search Console MCP

by saurabhsharma2u
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

indexing_status

Check Google Indexing API notification status or remaining daily Bing submission quota for a site URL.

Instructions

Check notification status for Google Indexing API or remaining daily Bing submission quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to check status for
typeNoCheck type (default: status)
engineNoTarget search engine
siteUrlYesThe site property URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.2
    • addedInput schema / properties / engine
      Added value: +{
+  "description": "Target search engine",
+  "enum": [
+    "google",
+    "bing",
+    "all"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / siteUrl / description
      Previous value: -"The property URL as registered in Search Console"New value: +"The site property URL"
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Check type (default: status)",
+  "enum": [
+    "status",
+    "quota"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / url / description
      Previous value: -"The URL to check notification status for"New value: +"URL to check status for"
    • changedInput schema / required
      Previous value: -[
-  "siteUrl",
-  "url"
-]New value: +[
+  "siteUrl"
+]
  2. First observedv1.14.2

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the action 'check' but does not state side effects, authentication requirements, rate limits, or return format. The description only lists what is checked without deeper behavioral context.

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?

The description is a single, front-loaded sentence with no redundant or extraneous words. It efficiently communicates the tool's core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has four parameters and no output schema, but the description does not explain return values or how the Google/Bing behaviors differ beyond the basics. The 100% schema coverage helps, but the description alone leaves gaps in expected output and parameter interaction.

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 description coverage is 100%, so a baseline of 3 is appropriate. The description adds some context by linking Google to notification status and Bing to quota, which hints at how engine and type parameters might be used, but it does not explicitly map parameters to actions.

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?

The description clearly states the tool checks notification status for Google Indexing API and remaining daily Bing submission quota, using a specific verb ('Check') and identifiable resources. This distinguishes it from sibling tools like indexing_submit, which handles submissions.

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?

The description implies use for checking status/quota but does not explicitly state when to use this tool versus alternatives like indexing_submit, nor does it provide any exclusions or conditions. Usage is implied rather than explicit.

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

Deploy Server

Other Tools