Skip to main content
Glama
Sign In

TRYIT

by com.inctryit
OverviewDiscussionsAdmin

Analyze a YouTube channel

analyze_channel
Read-onlyIdempotent

Reference-channel breakdown for a YouTube channel id (UC…): size, recent 30-video averages, engagement, top videos. 5 credits.

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_id": "<channel_id>"
    },
    "name": "analyze_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuinely new context: the 5-credit cost and the analytical window (recent 30-video averages, engagement, top videos). It stops short of describing behavior for invalid or private channel ids, 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?

A single dense sentence that front-loads the purpose, lists the returned metrics, and ends with the cost. Every clause carries information; nothing is redundant or padded.

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 one-parameter read-only tool with no output schema, the description covers scope, outputs, and cost well. The remaining gap is minor: no mention of pagination/limits on top videos or how failures (private/deleted channel) surface.

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?

Schema coverage is 0%, so the description must carry the burden, and it does provide a useful format cue — the id starts with 'UC…'. It does not clarify where to obtain the id or what happens if a handle (e.g. @name) is passed instead.

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 names a specific verb ('breakdown') and resource ('YouTube channel id (UC…)') and enumerates what the analysis covers: size, recent 30-video averages, engagement, top videos. It does not reference any sibling (e.g. similar_content, trending_items) to distinguish itself, so it falls short of a 5.

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?

Usage is only implied: an agent can infer this is for deep-diving a single known channel, but there is no explicit when-to-use vs when-not guidance and no mention of alternatives such as similar_content for discovery. No prerequisites or error conditions are stated.

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

All TRYIT toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources