Vee3

youtube.channel_search

Search public videos on a YouTube channel by keyword or phrase.

Accepts a bare channel id (for example UCJ5v_MCY6GNUBTO8-D3XoAg), not a URL. Returns matching video entries and cursorNext for pagination.

Use cursorNext from a prior response as cursor for the next page.

Cost = 10 tokens.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Search keywords or phrase within the channel.
`cursor`	No	Pagination cursor from cursorNext.
`channel_id`	Yes	YouTube channel id (for example UCJ5v_MCY6GNUBTO8-D3XoAg, not a URL).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`contents`	No	Matching video entries for the current page. Each entry includes a type field and nested video object.
`cursorNext`	No	Cursor for the next page, when available.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJun 21, 2026

changedOutput schema / $defs / YoutubeChannelSearchResponseContentsItemVideo / properties / badges / anyOf

Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/YoutubeChannelSearchResponseContentsItemVideoBadgesItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / $defs / YoutubeChannelSearchResponseContentsItemVideoBadgesItem

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "badge": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Badge label.",
-      "title": "Badge"
-    }
-  },
-  "title": "YoutubeChannelSearchResponseContentsItemVideoBadgesItem",
-  "type": "object"
-}

First observedJun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses cost (10 tokens), the required bare channel ID format, that only public videos are searched, and the pagination mechanism via cursorNext. This goes beyond the obvious read-only nature of a search, though it doesn't mention rate limits or authorization requirements.

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?

The description is four concise sentences, each earning its place: purpose, input constraint, output behavior with pagination, and cost. No redundant fluff, and the most important information (what it does) is front-loaded.

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 tool's moderate complexity (3 params, output schema present), the description covers the essential aspects: purpose, input format, pagination flow, and cost. Output schema handles return structure, so the description doesn't need to enumerate fields. It is complete enough for an agent to use it correctly.

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 all parameters are documented. The description adds value by explaining the purpose of cursorNext and how it relates to the cursor parameter, plus reiterating the bare ID requirement. This clarifies the intended usage flow beyond the schema's individual parameter descriptions.

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?

The description opens with a specific verb and resource: 'Search public videos on a YouTube channel by keyword or phrase.' This clearly distinguishes it from sibling tools like youtube.search (general YouTube search) and youtube.channel_videos (likely listing videos without keyword filtering). The scope is unambiguous.

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?

The description gives clear context: it's for searching within a specific channel using a bare channel ID, not a URL. It also provides pagination instructions with cursorNext. However, it doesn't explicitly mention when NOT to use this tool or point to alternatives like youtube.search for broader queries, so it stops short of a 5.

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

All Vee3 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.