instavision-mcp

Reset your dedup pool

reset_seen_accounts

DestructiveIdempotent

Clear the seen-accounts dedup pool to let accounts reappear in future discovery runs; pass all=true to wipe the entire pool (confirm=true required).

Instructions

DESTRUCTIVE. Clear your dedup pool. Default clears only your blocklist: handles you imported are removed, and accounts earlier runs delivered (or ruled out by follower count) go back to how they were before you blocklisted them. Pass all=true to delete the whole pool, run-collected entries included. Requires confirm=true.

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": {
      "confirm": "<confirm>"
    },
    "name": "reset_seen_accounts"
  }
}

Input Schema

Name	Required	Description	Default
`all`	No
`confirm`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations flag destructive/idempotent, but the description goes further by spelling out exactly what is destroyed ('handles you imported are removed') and the restoration semantics ('accounts earlier runs delivered ... go back to how they were before you blocklisted them'). It also discloses the confirm=true gate, which the schema does not explain.

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?

Four tight sentences, front-loaded with 'DESTRUCTIVE.' then the default behavior, the all=true variant, and the confirm requirement. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive reset with no output schema, everything needed to call it safely is present: blast radius of both modes, restoration effect, and the confirm gate.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry both parameters — and it does: all=true deletes the entire pool including run-collected entries, confirm=true is required. Semantics are clear, though types/enum-style constraints come only from the schema.

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?

Names a specific verb and resource ('Clear your dedup pool') and immediately scopes it: default clears only blocklist-imported handles, all=true wipes the whole pool. An agent can separate this from get_seen_accounts/add_seen_accounts without opening a schema.

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?

Gives a clear selection condition between the default and all=true modes and states the confirm prerequisite. It does not explicitly name sibling tools or when to prefer them over this reset, so it falls short of full routing guidance.

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

Deploy Server