Skip to main content
Glama
Sign In

BulkTranscripts YouTube

by co.bulktranscripts
OverviewDiscussionsAdmin

List a bulk job's results

list_bulk_results
Read-onlyIdempotent

One page of per-video outcomes for a bulk job: video id, title, channel, duration, word count and status (ok, cached, or error with a code). Never includes transcript text; every ok or cached video is in the library and free to read again. next_cursor from one page continues to the next. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "run_id": "<run_id>"
    },
    "name": "list_bulk_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, default 50.
cursorNonext_cursor from the previous page; omit for the first page.
run_idYesThe run_id of the bulk job.

Output Schema

NameRequiredDescriptionDefault
noteNo
itemsYes
totalNo
run_idYes
statusYes
next_cursorYesPass back as `cursor` for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / run_id / description
      Previous value: -"The run_id from start_bulk_extract."New value: +"The run_id of the bulk job."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "items": {
+        "properties": {
+          "channel": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "duration": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "error": {
+            "properties": {
+              "code": {
+                "type": "string"
+              },
+              "message": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "code",
+              "message"
+            ],
+            "type": "object"
+          },
+          "position": {
+            "type": "integer"
+          },
+          "status": {
+            "description": "ok, cached, error, skipped or quota.",
+            "type": "string"
+          },
+          "title": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "video_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "word_count": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "position",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "description": "Pass back as `cursor` for the next page; null on the last page.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "run_id": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "run_id",
+    "status",
+    "items",
+    "next_cursor"
+  ],
+  "type": "object"
+}
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description adds genuinely new behavioral context the annotations do not carry: no transcript text is returned, ok/cached results remain in the library, and the call is free.

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?

Four short sentences, front-loaded with what the page contains, followed by the exclusion, the library consequence, pagination, and cost. Every sentence carries distinct information and none is 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?

With an output schema present, the description need not restate the return shape, yet it still covers pagination continuation, cost, and the important negative constraint (no transcript text). An agent has everything it needs to call 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 all three parameters (run_id, limit, cursor) are already documented in the schema. The description restates cursor semantics ('next_cursor from one page continues to the next') without adding format or default detail, matching the baseline-3 case where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('one page of per-video outcomes for a bulk job') and enumerates the returned fields (video id, title, channel, duration, word count, status). It implicitly separates itself from get_bulk_status by focusing on per-video outcomes, but never names that sibling, so the differentiation is left to inference.

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?

Pagination guidance ('next_cursor from one page continues to the next') and a cost signal ('Free') are given, and the note that ok/cached videos are re-readable implies a follow-up path. However there is no explicit when-to-use statement relative to get_bulk_status or get_transcript, and no exclusions.

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