BulkTranscripts YouTube

Track new uploads (free)

get_latest_videos

Read-onlyIdempotent

Get a channel's newest uploads (up to 15) with publish dates, from YouTube's RSS feed (or a lightweight listing when the feed is unavailable). Always free — no credit charged — so it is ideal for monitoring channels, daily recaps, and 'did they post this week?' checks. Accepts @handle, URL, or UC… id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`channel`	Yes	Channel @handle, URL, or UC… id.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes
`source`	No	feed, or listing when the RSS feed was unavailable (then `published` may be null).
`channel`	No
`results`	Yes
`channel_id`	No
`billing_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "billing_note": {
+      "type": "string"
+    },
+    "channel": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "channel_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "count": {
+      "type": "integer"
+    },
+    "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"
+    },
+    "source": {
+      "description": "feed, or listing when the RSS feed was unavailable (then `published` may be null).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "results",
+    "count"
+  ],
+  "type": "object"
+}

First observedAug 22, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds valuable behavioral context: it is free (no credit charged), uses a specific data source (RSS feed) with a fallback (lightweight listing when feed unavailable), and caps results at 15. These details inform the agent about how the tool behaves at runtime, which the annotations do not provide.

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 compact and well-structured: the core action appears first, followed by the source and fallback, then pricing, then use cases, then accepted formats. Every sentence adds distinct value, and there is no filler.

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 single-parameter tool with an output schema, the description covers all necessary operational aspects: what it returns (uploads with publish dates), the limit, the data source and fallback, cost, and identifier formats. An agent has everything needed to invoke it appropriately without missing details.

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?

The schema description for 'channel' already explains 'Channel @handle, URL, or UC… id.' In the tool description, the same information is repeated ('Accepts @handle, URL, or UC… id.'). Since schema coverage is 100% and the description adds no new parameter-level detail, this stays at the baseline of 3.

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 ('get'), a specific resource ('a channel's newest uploads'), a limit ('up to 15'), and includes 'publish dates' – fully distinguishing it from siblings like search_channel or get_channel_videos. It is concrete and unambiguous about what the tool returns.

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 explicitly lists ideal use cases ('monitoring channels, daily recaps, and 'did they post this week?' checks'), giving clear context for when to call it. However, it does not mention when not to use it or alternatives, so it stops short of explicit exclusion 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 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?