Skip to main content
Glama
Sign In
video-url-analyzer-mcp

video-url-analyzer-mcp

by u2n4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cleanup_video_cache

Inspect and clean video cache files used by the video URL analyzer. Default dry-run prevents accidental deletion, allowing safe management of cached video data.

Instructions

Inspect or clean managed video cache files. Safe dry-run by default.

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

Input Schema

NameRequiredDescriptionDefault
scopeNosources
dry_runNo
video_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only mentions the default dry-run behavior, but lacks disclosure of destruction effects, permission requirements, or reversibility when dry_run is false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one sentence), which is efficient but sacrifices necessary detail. It is not tautological, but could be better structured to include parameter and behavioral info.

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

Completeness1/5

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

Given 3 parameters, 0% schema description coverage, and an output schema, the description is severely incomplete. It omits return values, parameter roles, and the tool's overall effect, leaving critical gaps for an agent.

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

Parameters1/5

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

Schema coverage is 0% and the description adds no parameter explanations. Terms like 'scope' and 'video_id' remain undefined, leaving the agent without guidance beyond the schema's basic types and defaults.

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 inspects or cleans managed video cache files, with a note about safe dry-run. The verb-resource pair is explicit, though it doesn't elaborate on what 'managed video cache files' are.

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?

No guidance is provided on when to use inspect vs. clean, or how this tool relates to siblings like delete_video_context. There are no explicit when-to-use or alternative recommendations.

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