ScriptHaul

List videos in a channel or playlist

list_videos

Read-onlyIdempotent

List the videos of a YouTube channel or playlist: date, video ID, and title for each. Use this to answer questions about a channel — pick the relevant videos by title, then call get_transcript for each one. Listings are cached for a few hours; a fresh enumeration counts against the same daily allowance as uncached fetches. Costs 0 credits. Example prompt: "List the videos in https://www.youtube.com/@TED."

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": {
      "url": "<url>"
    },
    "name": "list_videos"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	YouTube channel or playlist URL (also accepts @handles).
`limit`	No	Maximum videos to list, newest first for channels. Default 100, maximum 200.

Output Schema

Name	Required	Description
`type`	Yes
`shown`	Yes	How many are included below (bounded by limit).
`title`	No	Channel or playlist title when known.
`videos`	Yes
`truncated`	No	True when the source has more videos than one enumeration returns (500).
`video_count`	Yes	Total videos in the listing snapshot.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations, the description discloses caching behavior, daily allowance implications for fresh enumerations, and the zero-credit cost. These are operationally important details an agent would not know from readOnlyHint, openWorldHint, or idempotentHint alone.

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 description is front-loaded with the core purpose, then moves efficiently into usage and cost/caching notes. The example prompt is helpful but slightly optional, keeping it short of maximally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple two-parameter schema, full schema coverage, existing annotations, and an output schema, the description supplies everything necessary to select and invoke the tool. It also adds useful operational context without over-explaining return values.

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%, and both parameters are already documented in the input schema. The description reinforces that the URL can refer to a channel or playlist, but adds no meaningful detail about the limit parameter or URL format beyond what the schema provides.

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 states a specific verb and resource: listing videos from a YouTube channel or playlist, with date, video ID, and title returned. It distinguishes the follow-up use of get_transcript, but does not clearly differentiate this tool from the sibling get_latest_videos, which an agent may see as an overlapping alternative.

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

Usage Guidelines4/5

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

It clearly says to use this when answering questions about a channel and instructs the agent to select relevant videos by title then call get_transcript for each. That is strong when-to-use guidance, but it does not state when to prefer this over get_latest_videos or when not to use it.

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

All ScriptHaul tools Inspect

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

Need Help?