BulkTranscripts YouTube

Search inside a channel

search_channel

Read-onlyIdempotent

Search within one channel's uploads to find its videos on a topic — great for researching what a creator has said about something without listing the whole archive. Accepts @handle, channel URL, or UC… id. Costs 1 credit.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results, default 10.
`query`	Yes	Topic to search for within the channel.
`channel`	Yes	Channel @handle, URL, or UC… id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`query`	Yes
`billing`	Yes
`channel`	Yes
`results`	Yes
`channel_title`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "billing": {
+      "properties": {
+        "creditsCharged": {
+          "description": "Credits this call cost (0 on cache hits).",
+          "type": "integer"
+        },
+        "enabled": {
+          "type": "boolean"
+        },
+        "freeLimit": {
+          "type": "integer"
+        },
+        "granted": {
+          "type": "integer"
+        },
+        "kind": {
+          "description": "anon (free tier), license (paid) or admin.",
+          "type": "string"
+        },
+        "remaining": {
+          "description": "Credits left on this account.",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "unlimited": {
+          "type": "boolean"
+        },
+        "used": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "enabled"
+      ],
+      "type": "object"
+    },
+    "channel": {
+      "type": "string"
+    },
+    "channel_title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "count": {
+      "type": "integer"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "channel": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "channel_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "duration": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "published": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "enum": [
+              "video",
+              "channel",
+              "playlist"
+            ],
+            "type": "string"
+          },
+          "url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "view_count": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "channel",
+    "query",
+    "results",
+    "count",
+    "billing"
+  ],
+  "type": "object"
+}

First observedAug 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds the unique cost of 1 credit and clarifies accepted channel formats, which are useful operational facts beyond the schema. No contradiction with annotations.

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?

Two concise sentences with no filler. The purpose is front-loaded, followed by use case, accepted formats, and cost – each earning its place. Efficient and scannable.

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?

For a simple read-only search tool with an output schema, the description covers purpose, use case, input formats, and cost. Nothing an agent needs to decide whether to call it or how to call it correctly is missing.

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 channel, query, and limit. The description repeats the channel format but adds no new semantic detail about query or limit, keeping it at the baseline.

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 ('one channel's uploads') with the intent of finding videos on a topic. The description explicitly distinguishes it from listing the whole archive, which separates it from get_channel_videos and positions it against the broader search_youtube.

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?

Gives a clear use case ('researching what a creator has said about something') and implies a channel-scoped alternative to global search. It does not explicitly name sibling tools or provide when-not-to-use guidance, but the 'without listing the whole archive' hint covers the main exclusion.

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

All BulkTranscripts YouTube 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?