Skip to main content
Glama

BulkTranscripts YouTube

by co.bulktranscripts
OverviewDiscussionsAdmin

List a channel's videos

get_channel_videos
Read-onlyIdempotent

List the videos of a YouTube channel (id, title, duration, URL) without fetching transcripts. Accepts @handle, channel URL, or UC… channel id. Costs 1 credit. Chain into get_transcripts to bulk-extract.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax videos to list, default 100.
channelYesChannel @handle, URL, or UC… id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
titleNo
billingYes
channelYes
resultsYes
has_moreNoTrue when the listing stopped at `limit`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "has_more": {
+      "description": "True when the listing stopped at `limit`.",
+      "type": "boolean"
+    },
+    "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"
+    },
+    "title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "channel",
+    "results",
+    "count",
+    "billing"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark the tool as readOnly, idempotent, and non-destructive, and the description adds useful behavioral detail: it costs 1 credit, returns specific fields, skips transcripts, and accepts multiple identifier formats. No contradiction exists between the description and 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?

The description is three tight sentences with no filler: core function and output fields, accepted input formats and credit cost, and a downstream workflow hint. Every sentence earns its place, and the most important purpose information 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?

With an output schema present and readOnly/idempotent annotations provided, the description covers everything an agent needs to call the tool correctly: what it returns, accepted inputs, cost, no-transcript behavior, and the natural next step for bulk extraction. Nothing essential 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%, and both parameters already have meaningful schema descriptions. The description's 'Accepts @handle, channel URL, or UC… channel id' repeats the channel schema text rather than adding new semantics, and the limit parameter's default and range live only in the schema. 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?

The description states a specific verb and resource: 'List the videos of a YouTube channel' and names the returned fields (id, title, duration, URL). It also explicitly distinguishes itself from transcript-fetching tools by saying it does so 'without fetching transcripts', and it names accepted channel identifier formats. This clearly differentiates it from sibling tools like get_transcripts and get_latest_videos.

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 is for listing a channel's videos and for not fetching transcripts, and it recommends a follow-up workflow via 'Chain into get_transcripts'. It does not explicitly enumerate exclusions versus get_latest_videos, search_channel, or get_playlist_videos, but the channel-scoped purpose and chain instruction are sufficient directional guidance.

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

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