Skip to main content
Glama
jedarden

YouTube Transcript DL MCP Server

by jedarden

get_cache_stats

Retrieve cache statistics and performance metrics for the YouTube transcript download server to monitor efficiency and track usage patterns.

Instructions

Get cache statistics and performance metrics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_cache_stats' tool. It calls the transcript service to get cache statistics and returns them as a formatted JSON text response.
    private async handleGetCacheStats() {
      const stats = this.transcriptService.getCacheStats();
      
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(stats, null, 2)
        }]
      };
    }
  • Registration of the 'get_cache_stats' tool in the list of available tools, including its name, description, and empty input schema.
    {
      name: 'get_cache_stats',
      description: 'Get cache statistics and performance metrics',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Input schema definition for the 'get_cache_stats' tool, which requires no parameters.
    inputSchema: {
      type: 'object',
      properties: {}
    }
  • Helper method in YouTubeTranscriptService that retrieves cache statistics by delegating to the underlying Cache instance.
    public getCacheStats() {
      return this.cache.getStats();
    }
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. While 'Get' implies a read operation, the description doesn't specify whether this requires authentication, what format the statistics are returned in, or if there are any rate limits. This leaves significant gaps for a tool with zero annotation coverage.

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 that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 that there are no annotations and no output schema, the description is incomplete. It doesn't explain what 'cache statistics and performance metrics' include, how they're formatted, or any behavioral aspects like error handling. For a tool with zero structured metadata, this minimal description leaves too many questions unanswered.

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 has 0 parameters, and the schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for this scenario is 4, as the description appropriately doesn't waste space on non-existent 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 clearly states the action ('Get') and the resource ('cache statistics and performance metrics'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling tools (like clear_cache or format_transcript), which would be needed for a perfect score.

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 any context, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name alone.

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