Skip to main content
Glama
Sign In
yt-analytics-mcp

yt-analytics-mcp

by KewkLW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

yt_get_analysis

Retrieve the full cached analysis JSON for a specific YouTube channel, including transcripts and computed metrics like WPM, profanity, and humor taxonomy.

Instructions

Retrieve the full cached analysis JSON for a specific channel.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channel": "<channel>"
    },
    "name": "yt_get_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesChannel name or slug (as returned by yt_list_analyses)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It identifies the operation as a retrieval (non-destructive) but fails to disclose caching behavior, error conditions, authentication needs, or what 'full cached analysis JSON' entails beyond a vague label.

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 sentence with zero wasted words, front-loading the purpose and resource. It is optimally concise for the information provided.

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 no output schema and no annotations, the description is too brief. It does not explain the returned JSON content, error handling, prerequisites (e.g., existing analysis), or any side effects. A retrieval of 'full cached analysis' warrants more completeness.

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 description coverage is 100% (the single parameter has a clear description referencing yt_list_analyses). The tool description adds no additional semantic meaning beyond what the schema already provides, so baseline score 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'retrieve' and explicitly names the resource 'full cached analysis JSON for a specific channel'. It clearly distinguishes from sibling tools like yt_list_analyses (listing) and yt_analyze_channel (analysis creation).

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 context via the parameter reference to yt_list_analyses, but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites.

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