Skip to main content
Glama

snapshot_stats

Captures and stores Bing Webmaster statistics locally to enable historical trend comparison. Run weekly because Bing data updates weekly.

Instructions

Take a snapshot of current Bing stats and store locally for historical comparison. Data updates weekly, so snapshot weekly.

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>"
    },
    "name": "snapshot_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlYesThe site URL
statsTypeNoType of stats to snapshot (default: all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully reveals that state is persisted locally and why (historical comparison) plus the weekly data refresh cadence. It does not say what happens on repeated snapshots for the same site (overwrite vs. append), where data is stored, or what the call returns, which matters for a write/persist operation.

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 short sentences, no filler, with the action and its rationale front-loaded and the cadence advice second. Every clause earns its place.

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 two-parameter tool whose schema fully documents inputs and which needs no output schema, the description covers what it does and when. The only real omission is repeated-snapshot/overwrite semantics for the same siteUrl, a minor but relevant gap.

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 both siteUrl and the statsType enum (with its "default: all" note) are already fully documented structurally. The description adds no meaning beyond the schema about scope or interplay between statsType values. Baseline 3 is appropriate.

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 uses a specific verb+resource ("Take a snapshot of current Bing stats") and states the persistence purpose ("store locally for historical comparison"). It is distinguishable from the live-fetch siblings like bing_get_query_stats and from list_snapshots, though it never names those alternatives, so sibling differentiation is left implicit.

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?

It supplies concrete timing guidance: "Data updates weekly, so snapshot weekly." That tells the agent when to invoke it. It stops short of exclusions or routing to alternatives (e.g., use diff_stats to compare, list_snapshots to browse), so it is clear context without explicit alternatives.

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