Skip to main content
Glama
Sign In

mowteng

by app.mowteng
OverviewDiscussionsAdmin

Compare Google and Bing queries

insights_google_vs_bing
Read-only

Compare the same site's queries in Google and Bing: the largest position gaps, and queries that appear in only one engine. Bing data is weekly, so the period is approximate. Needs Bing connected.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteUrl": "<siteUrl>",
      "bingSiteUrl": "<bingSiteUrl>"
    },
    "name": "insights_google_vs_bing"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLength of each period in days (7-90), ending 3 days before today because Search Console data lags. Defaults to 28.
limitNoMaximum results (1-200). Defaults to 20.
siteUrlYesSearch Console property exactly as gsc_list_sites returns it: "https://example.com/" or "sc-domain:example.com"
bingSiteUrlYesBing site URL exactly as bing_list_sites returns it, e.g. https://example.com/

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and a closed world, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: the Bing connection prerequisite and the caveat that Bing data is weekly so the period is approximate. However it says nothing about how missing Bing data or empty results are handled, and there is no output schema to fall back on, leaving a gap for a comparison tool.

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?

Two sentences, with the purpose and the enumerated outputs front-loaded and the caveat plus prerequisite trailing. Every clause carries information; there is no filler.

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 read-only tool with a fully documented schema, the description covers purpose, prerequisites and a data-quality caveat. It falls slightly short on result behavior, such as what a query missing from one engine looks like in the response and whether results are capped across both engines, but no output schema exists to compensate.

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 all four parameters including day ranges, limits and both site URL formats are already documented precisely in the schema. The description adds only the indirect hint that the period is approximate because of Bing's weekly granularity; it does not explain the two required site URLs or how they must correspond. Baseline 3 is appropriate.

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 names a specific verb and resource ('Compare the same site's queries in Google and Bing') and enumerates the two outputs, largest position gaps and single-engine queries. This clearly separates it from single-source siblings like gsc_search_analytics and bing_search_stats without requiring the schemas to be opened.

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?

'Needs Bing connected' is a concrete prerequisite, and the output framing implies the tool is for cross-engine gap analysis. It never names an alternative (e.g. use bing_search_stats for Bing-only) or an explicit when-not case, so the routing guidance stops just short of a 5.

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

All mowteng toolsInspect
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