Skip to main content
Glama

Latest from channels

latest_from_channels
Read-only

See what several channels uploaded most recently, in one call: the newest videos of each channel, newest first. Use it as a watchlist ("anything new from these creators?"), then skim the new videos with get_transcripts_batch or check them for a topic with find_in_videos. Up to 5 channels per call, or 25 on the Ultra plan; each channel counts as one request.

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": {
      "channels": "<channels>"
    },
    "name": "latest_from_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelsYesChannels as @handles, channel URLs or playlist URLs.
per_channelNoHow many recent videos per channel. Default 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld), so the description's addition of ordering semantics ('newest first') and quota behavior ('each channel counts as one request') is genuinely additive beyond structured fields. It stops short of describing what a channel with no recent uploads or an invalid handle returns, which would be the remaining behavioral gap.

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?

Two sentences, front-loaded with the core behavior, then the use case, then follow-up routing, then limits. Every clause carries information an agent would act on; there is no restatement of the title or 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?

For a two-parameter read tool with annotations and no output schema, the description covers purpose, ordering, quotas, and downstream chaining — enough to call it correctly. The omission of error/empty behavior for bad handles or channels without recent uploads is the only meaningful gap, and it is minor.

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 the baseline is 3, but the description adds a constraint the schema does not express: the effective channel cap is 5 per call rather than the schema's maxItems of 25, with 25 reserved for the Ultra plan. That resolves a potential mismatch an agent would otherwise hit only at call time.

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?

States a concrete verb and resource — 'See what several channels uploaded most recently' — and pins the scope: newest videos per channel, newest first, across multiple channels in one call. That scope explicitly distinguishes it from single-channel siblings like list_channel_videos and from keyword-based ones like search_youtube_videos.

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?

Gives a named use case ('Use it as a watchlist — anything new from these creators?') and routes the agent to concrete next steps: get_transcripts_batch to skim, find_in_videos to check a topic. Plus operational limits (5 channels, 25 on Ultra). Nothing is left to inference.

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.