Skip to main content
Glama

recent_clear

Clear played-at times and play counts from your media library while preserving scanned metadata, so you can reset watch history without rescanning files.

Instructions

Forget the play history. Scanned library metadata is kept — only the played-at times and counts are cleared.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does the most important thing for a destructive zero-param tool: it delineates exactly what is destroyed (played-at times, counts) versus what is preserved (scanned library metadata). It does not state irreversibility, confirmation requirements, or whether the action is undoable, which keeps it from a 5.

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, front-loaded with the action and immediately followed by the scope guarantee. Nothing is padded and no sentence is redundant.

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 single-action, zero-parameter destructive tool with no annotations and no output schema, the description supplies the essential information: what data is removed and what survives. The remaining gap is behavioral (irreversibility, whether a confirmation is needed) rather than structural.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no misleading parameter claims are made.

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?

"Forget the play history" gives a specific verb and resource, and the second sentence defines the exact boundary of the operation: played-at times and counts are erased, scanned library metadata survives. It stops short of naming the sibling it complements (recent_files), so an agent must infer that relationship, but the scope is unambiguous.

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 description implies usage (clearing watch/play history) but never states when an agent should call this versus reading recent files first or using other clear-style siblings like bookmark_clear. No preconditions, no exclusions, no named alternative.

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

Deploy Server

Other Tools