Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

youtube_channel_search

Search a YouTube channel's videos by channel ID, @handle, or URL. Returns video titles, URLs, durations, view counts and a pagination token.

Instructions

Search within a YouTube channel. Searches the videos of one YouTube channel for the required q. id accepts a channel id, @handle, /c or /user path, or a full channel URL. Items carry the video id, title, URL, duration, view count, published text and thumbnail, and the response echoes the resolved query. Page with continuation_token.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
idYesChannel ID, @handle, /c path, /user path, or full YouTube channel URL
continuation_tokenNoPagination token returned by a previous request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned item fields (video id, title, URL, duration, view count, published text, thumbnail), notes the response echoes the resolved query, and explains pagination via continuation_token. It omits auth/rate-limit or ordering behavior, but covers the essentials for a read tool.

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?

Front-loaded with the core purpose in the first clause, followed by tightly packed, non-redundant detail on id formats, return fields, and pagination. No filler sentences.

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?

No output schema exists, so the description compensates by describing returned fields and pagination. Combined with the fully covered input schema, an agent has everything needed to call it correctly and interpret the result.

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 the schema already documents q, id, and continuation_token. The description largely restates the accepted id formats and that q is required, adding only marginal meaning (the echoed resolved query). Baseline 3 is appropriate.

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 specific verb (search) and resource (videos within one YouTube channel), and the scoping phrase 'within a YouTube channel' cleanly separates it from global search tools like youtube_search and from listing tools like youtube_channel_videos. An agent can identify its role without opening the schema.

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 implied by the scope phrase 'searches the videos of one YouTube channel,' but the description never states when to prefer this over youtube_search or youtube_channel_videos, nor any exclusions or prerequisites. The context is inferable but not explicit.

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

Deploy Server

Other Tools