Skip to main content
Glama

job_youtube_channel

A YouTube channel's latest videos

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_url": "<channel_url>"
    },
    "name": "job_youtube_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_urlYespattern https://(www\.)?youtube\.com/(@[A-Za-z0-9._-]{1,100}|channel/UC[A-Za-z0-9_-]{22}|c/[A-Za-z0-9._-]{1,100}|user/[A-Za-z0-9._-]{1,100})/?
max_resultsNodefault 30, at most 500

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: no ordering guarantee, no pagination behavior, no indication of whether this is a read-only public fetch or requires credentials, and no rate-limit or quota context. 'Latest' is the only behavioral hint, weakly implying reverse-chronological ordering.

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

Conciseness2/5

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

Five words with no verb and no structure beyond a single noun phrase; this is under-specification rather than concision. Nothing is wasted, but the brevity leaves the definition unable to answer basic selection and invocation questions.

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?

For a tool with no annotations, no output schema, and two parameters whose behavior depends on filtering choices, the definition should at minimum describe what comes back and how results are bounded. None of that is present, so an agent cannot predict the response shape or result ordering.

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%, with channel_url carrying a full URL pattern and max_results documenting its default of 30 and cap of 500, so the schema already does the work. The description adds no extra meaning about what max_results counts (videos, shorts, live streams) or how channel_url forms map to each other.

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

Purpose3/5

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

The phrase 'A YouTube channel's latest videos' identifies the resource (a channel's recent uploads) but is a noun fragment with no verb, so it never states that the tool retrieves or lists anything. It does implicitly separate it from job_youtube_comments, job_youtube_search, and job_youtube_transcript by naming videos from a channel, but the phrasing is closer to a label than a purpose statement.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to prefer job_youtube_search or job_youtube_comments instead, and no prerequisites such as whether a public channel URL is sufficient. The agent must infer the calling context entirely from the tool name.

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