Skip to main content
Glama

YouTube shorts

run_youtube_shorts
Read-onlyIdempotent

Get the shorts of a YouTube channel: title, views, likes, comments, hashtags, date and the channel's subscribers, total videos and views. 2 points per returned record.

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

Input Schema

NameRequiredDescriptionDefault
channelYesChannel (@handle or URL). e.g. @NASA
sort_byNoSort shorts by. Options: POPULAR = Popular, OLDEST = Oldest
max_itemsNoMax shorts (up to 1000) Default: 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 openWorld, so the safety profile is covered. The description adds real value beyond that with the metered cost ("2 points per returned record") and the exact shape of what comes back, which lets an agent budget calls. It omits pagination/truncation behavior and how sorting interacts with cost.

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 front-loaded sentence: purpose first, return payload second, cost last. No filler, and the cost caveat is placed where it will be read before invocation.

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?

With no output schema, the field enumeration (title, views, likes, comments, hashtags, date, channel stats) carries the return-value burden well. Remaining gaps are minor but real: no statement of what happens past max_items (pagination or truncation) and no default sort behavior, both of which matter for a 3-param list tool.

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%, so channel format, sort enum options and max_items bounds/default are already documented in structured fields. The description adds no parameter-level meaning; the "2 points per returned record" line only indirectly hints that max_items should be tuned. Baseline 3 applies.

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?

States a specific verb+resource ("Get the shorts of a YouTube channel") and enumerates the returned fields, which makes it distinguishable from run_youtube_comments and run_youtube_search. It never explicitly contrasts itself with run_youtube_channel, whose subscriber/total-video data it partly duplicates, so sibling differentiation is implicit rather than stated.

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 by the resource name — an agent can infer "call this when you want shorts from a channel", but there is no when-to-use framing, no exclusivity conditions, and no named alternatives (e.g. use run_youtube_channel for channel metadata). The cost note is pricing, not selection guidance.

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.

Resources