Skip to main content
Glama

diff_stats

Compare two Bing Webmaster snapshots by site, stats type, and dates to identify query or page performance changes between them.

Instructions

Compare two snapshots to see what changed between them.

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>",
      "statsType": "<statsType>",
      "date1": "<date1>",
      "date2": "<date2>"
    },
    "name": "diff_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
date1YesFirst snapshot date (ISO format)
date2YesSecond snapshot date (ISO format)
siteUrlYesThe site URL
statsTypeYesType of stats to compare

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it doesn't explain what a "change" is (new, lost, or moved entries), whether date1 is treated as baseline or comparison, or whether the result is a delta or a full listing. These are exactly the details a diff tool must surface.

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?

A single short sentence with the comparison outcome front-loaded and no filler. It is efficient, though the brevity comes at the cost of specification rather than being genuinely complete.

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?

For a four-parameter, no-annotation, no-output-schema comparison tool, the definition leaves out directionality of the diff and the shape of the result. An agent can guess it returns changes, but cannot confidently describe or interpret the output.

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% with four documented required params, including an enum for statsType, so the baseline is 3. The description adds no meaning beyond the schema — notably it never clarifies the ordering semantics of date1 versus date2, which is the one thing a diff tool most needs to state.

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?

"Compare two snapshots" gives a specific verb plus resource, and "to see what changed" states the outcome. It does not, however, distinguish this from siblings like snapshot_stats or ai_compare_with_bing_stats, nor does it say what kind of stats are compared beyond the schema's enum.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus snapshot_stats, list_snapshots, or ai_compare_with_bing_stats, and no prerequisites such as needing two existing snapshots of the same site and statsType. The only implied usage is the generic "see what changed" clause.

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