Skip to main content
Glama

list_snapshots

Retrieve all saved snapshots for a site URL to review historical citation reports and track changes over time.

Instructions

List all saved snapshots for a site.

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": "list_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It implies a passive read but says nothing about pagination, ordering, whether the response is truncated, what a snapshot record contains, or whether auth/site ownership is required. For a list operation returning an unbounded set, the absence of pagination or size hints is a real gap.

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?

One sentence with no filler; the resource and its scope are stated immediately. Nothing is repeated from the schema and nothing could be cut without losing meaning.

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?

For a one-parameter read tool with no output schema and no annotations, the description covers the basics but omits what a 'snapshot' is and how results are shaped or bounded. Adequate to select the tool, thin for predicting its 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% for the single siteUrl parameter, so the schema already defines the input. The description only echoes that the listing is per-site and adds no format or scoping nuance beyond it, which is the baseline case for fully documented params.

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?

States a specific verb and resource ('List all saved snapshots') plus the scoping entity ('for a site'), so the agent knows exactly what is returned. It does not differentiate from the sibling snapshot_stats, which likely surfaces aggregate metrics over the same resource, leaving the read-vs-stats distinction to inference.

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 call this versus snapshot_stats or the bing_* list tools, and no prerequisites or exclusions are mentioned. The agent must guess from tool names alone.

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