Skip to main content
Glama
jedarden

YouTube Transcript DL MCP Server

by jedarden

clear_cache

Remove stored YouTube transcript data to free storage space and ensure fresh transcript retrieval for the YouTube Transcript DL MCP Server.

Instructions

Clear the transcript cache

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary handler function for the 'clear_cache' MCP tool. Delegates cache clearing to the YouTubeTranscriptService and returns a standardized success response.
    private async handleClearCache() {
      this.transcriptService.clearCache();
      
      return {
        content: [{
          type: 'text',
          text: 'Cache cleared successfully'
        }]
      };
    }
  • Core implementation that actually clears the transcript cache by flushing the internal Cache instance.
    public clearCache(): void {
      this.cache.flush();
    }
  • Tool registration in the list of available tools, including schema definition (no input parameters required).
    {
      name: 'clear_cache',
      description: 'Clear the transcript cache',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Clear' implies a destructive mutation, but the description doesn't specify whether this is reversible, what permissions are needed, or what happens to system performance. It lacks details on rate limits, side effects, or return values, which is a significant gap for a mutation tool.

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?

The description is a single, efficient sentence with no wasted words. It's front-loaded and directly states the tool's purpose, making it highly concise and well-structured for quick understanding.

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 complexity of a destructive cache-clearing operation with no annotations and no output schema, the description is incomplete. It doesn't explain behavioral aspects like safety, permissions, or what to expect after execution, which are critical for such a tool.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, earning a baseline score of 4 for tools with no parameters.

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 'Clear the transcript cache' clearly states the action (clear) and target resource (transcript cache). It uses a specific verb and identifies the resource, though it doesn't explicitly differentiate from sibling tools like 'get_cache_stats' or 'list_transcripts' beyond the action type.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, consequences, or relationships to sibling tools like 'get_cache_stats' for monitoring or 'list_transcripts' for accessing cached data, leaving usage context unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jedarden/yt-transcript-dl-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server