Skip to main content
Glama

reset_seen

Clears the sent-content history for Bilibili or Douyin so list_feed can include previously sent items again; intended only for deliberate resets.

Instructions

清空「已发过」记录,让 list_feed 重新发旧内容(一般不用)。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reset_seen"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNo平台

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/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 does disclose the key side effect that previously-sent items will be re-delivered by list_feed. It does not say whether the reset is reversible, whether re-sending is immediate or on the next list_feed call, or whether it affects only the given platform or all platforms.

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?

A single short sentence: action first, consequence second, caveat last. Nothing is wasted and the ordering is front-loaded.

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?

With no annotations, no output schema, and one optional parameter, the description covers the core effect but leaves state-reversibility, re-send timing, and platform scope unspecified. Acceptanceable but not complete for an operation that mutates delivery state.

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 coverage is 100% and the single parameter is an enum with a description ('平台'), so the schema already documents it. The description does not clarify whether the optional platform scopes the reset to one platform or defaults to all, which is the one piece of meaning it could add.

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 gives a specific verb ('清空' clear) and the state it targets ('已发过' already-sent records), plus the downstream effect (list_feed re-sends old content). It implicitly distinguishes itself from the listing sibling by describing a state reset rather than a read. The only shortfall is that the abstract 'seen records' is not tied to a concrete stored resource.

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

Usage Guidelines3/5

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

The parenthetical '(一般不用)' (generally not needed) gives a caution but no positive condition for when it IS warranted, and no explicit alternative is named. An agent learns default behaviour (avoid) but not the trigger case (e.g. after content edits or to force a re-push).

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