Skip to main content
Glama
saurabhsharma2u

Search Console MCP

by saurabhsharma2u
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

compare_engines

Compare your site's search performance across Google Search Console and Bing Webmaster Tools. Identify metric gaps and opportunities to improve visibility in both engines.

Instructions

Cross-engine performance matrix comparing Google Search Console vs Bing Webmaster Tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResult row limit
endDateNoEnd date YYYY-MM-DD
siteUrlYesThe site property URL
dimensionNoComparison dimension
startDateNoStart date YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.0.2
    • changedInput schema / properties / dimension / description
      Previous value: -"Dimension to compare"New value: +"Comparison dimension"
    • changedInput schema / properties / dimension / enum
      Previous value: -[
-  "query",
-  "page",
-  "country",
-  "device"
-]New value: +[
+  "query",
+  "page"
+]
    • changedInput schema / properties / endDate / description
      Previous value: -"End date (YYYY-MM-DD)"New value: +"End date YYYY-MM-DD"
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows to return per engine (default: 1000)"New value: +"Result row limit"
    • removedInput schema / properties / minClicks
      Removed value: -{
-  "description": "Minimum clicks threshold",
-  "type": "number"
-}
    • removedInput schema / properties / minImpressions
      Removed value: -{
-  "description": "Minimum impressions threshold",
-  "type": "number"
-}
    • removedInput schema / properties / offset
      Removed value: -{
-  "description": "Offset for pagination",
-  "type": "number"
-}
    • changedInput schema / properties / siteUrl / description
      Previous value: -"The URL of the site"New value: +"The site property URL"
    • changedInput schema / properties / startDate / description
      Previous value: -"Start date (YYYY-MM-DD)"New value: +"Start date YYYY-MM-DD"
    • changedInput schema / required
      Previous value: -[
-  "siteUrl",
-  "dimension",
-  "startDate",
-  "endDate"
-]New value: +[
+  "siteUrl"
+]
  2. First observedv1.14.2

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states it compares GSC vs Bing, without explaining whether it performs read-only API calls, what data source it accesses, authentication needs, or how results are structured. For a multi-source comparison tool, this is a significant gap.

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?

The single-sentence description is concise and front-loaded with the core purpose. It lacks a bit of useful structure but contains no wasted words, earning a strong but not perfect score.

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

Completeness2/5

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

With 5 parameters, no output schema, no annotations, and only a one-line description, the tool's invocation context is under-specified. The description doesn't clarify optional parameter defaults, return format, or how the comparison matrix is built, making it insufficient for an agent to reliably use the tool.

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 the input schema already documents all five parameters. The description adds no parameter semantics beyond the schema, but the baseline of 3 is warranted since the schema fully covers parameter meaning.

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?

The description names a specific resource ('Cross-engine performance matrix comparing Google Search Console vs Bing Webmaster Tools'), making the tool's purpose clear. It doesn't explicitly differentiate from siblings like analytics_compare, so it stops short of a 5.

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 phrase 'Cross-engine performance matrix' implies use when comparing GSC and Bing metrics, but the description provides no explicit when-to-use guidance or alternatives. A clear context is absent beyond the comparison intent, so usage is only implied.

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