Skip to main content
Glama

Check a video channel

video_channel
Read-onlyIdempotent

Use to list a YouTube channel's uploads. Returns every upload on the channel, read 50 at a time and sorted by views. Give handle or, without one, the channel id. The per-check tally needs a Watch licence and is not offered here. Read-only. For the checks on one video use video_check.

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

Input Schema

NameRequiredDescriptionDefault
idNoChannel id, if no handle
handleNo@channel handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotency, and non-destructiveness, but the description adds genuinely new behavior: results are sorted by views and returned 50 at a time, and the per-check tally is excluded for licence reasons. It stops short of explaining how an agent continues past the first 50 items, which is the main remaining ambiguity.

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

Conciseness4/5

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

The sentences are short and front-loaded with purpose, then returning behavior, then parameters, then the sibling pointer. "Read-only" lightly duplicates the readOnlyHint annotation, but the rest of the text carries no filler.

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?

There is no output schema, so the description carries the return contract, and it does say the list covers every upload, sorted by views, paged at 50. It does not describe the fields on each upload entry, which leaves a modest gap for an open-world listing 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?

Schema coverage is 100%, so a 3 would be the floor, but the description adds precedence semantics the schema does not: supply a handle, or fall back to the channel id when no handle is available. That resolves which of the two optional parameters to prefer.

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 opens with a specific verb and resource ("list a YouTube channel's uploads") and explicitly contrasts itself with the sibling video_check, which covers per-video checks. An agent can select between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to use this tool, names the alternative (video_check) with the exact condition that selects it (checks on one video), and rules out an expectation (the per-check tally is not offered here). Preconditions are covered by the handle-vs-id instruction.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.