@scom82/topvisor-mcp

topvisor_get_snapshots

Fetch SERP snapshots for keywords in a project region by specifying a date range or specific dates.

Instructions

Get SERP snapshots for a project and region. Snapshots are collected when do_snapshots=1 is set in topvisor_check_positions. Returns snapshotsData per keyword. Requires either 'dates' array OR both 'date1' and 'date2'.

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": {
      "project_id": "<project_id>",
      "region_index": "<region_index>"
    },
    "name": "topvisor_get_snapshots"
  }
}

Input Schema

Name	Required	Description
`project_id`	Yes
`region_index`	Yes	Region index (from topvisor_list_regions, NOT region_key)
`date1`	No	YYYY-MM-DD start date (use with date2)
`date2`	No	YYYY-MM-DD end date (use with date1)
`dates`	No	Array of specific YYYY-MM-DD dates. Use either dates OR date1+date2 — both cannot be absent.
`filters`	No	Keyword filters, max 100 per request
`type_range`	No	Date range type (default 3)
`count_dates`	No
`show_exists_dates`	No
`show_ams`	No
`positions_fields`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the return type (snapshotsData per keyword) but lacks information about side effects, permissions, rate limits, or data freshness. The cross-reference to another tool is helpful but insufficient.

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 description is concise with three sentences, each serving a purpose: purpose, context, and constraint. No wasted words, but it could be better organized with bullet points or clearer separation of parameter usage.

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?

Given the tool has 11 parameters, no output schema, and no annotations, the description is incomplete. It does not explain what snapshotsData contains, how filters work, or the meaning of type_range, count_dates, etc. More detail is needed for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 55%, and the description repeats the constraint about date parameters already present in the schema. It adds no new meaning for other parameters like filters, type_range, or count_dates. The description fails to compensate for low schema coverage.

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 clearly states the tool retrieves SERP snapshots for a project/region. It uses specific verbs and resources. However, it does not explicitly differentiate from sibling tools like topvisor_get_history or topvisor_get_summary, which might cause confusion.

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?

Provides a constraint about date parameters but no guidance on when to use this tool versus alternatives. No mention of when not to use it or prerequisites beyond the cross-reference to topvisor_check_positions.

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

Deploy Server