BulkTranscripts YouTube

Check a bulk job

get_bulk_status

Read-onlyIdempotent

Progress of a bulk extraction job: status (running, completed, stopped, failed), total, completed, failed, skipped (no captions), quota (not attempted for lack of credits), remaining, and check_again_in_seconds, the suggested wait before the next check (0 means the job is finished). 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": "get_bulk_status"
  }
}

Input Schema

Name	Required	Description	Default
`run_id`	Yes	The run_id of the bulk job.

Output Schema

Name	Required	Description
`error`	No
`phase`	No
`quota`	No	Videos not attempted because credits ran out.
`total`	No
`cached`	No
`failed`	No
`run_id`	Yes
`source`	Yes
`status`	Yes	running, completed or stopped.
`billing`	Yes
`skipped`	No	Videos without captions; never charged.
`stopped`	No
`completed`	No
`remaining`	No
`interrupted`	No
`videos_found`	No	Null until a large channel has been listed.
`check_again_in_seconds`	Yes	Do not poll sooner than this.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / run_id / description

Previous value: -"The run_id from start_bulk_extract."New value: +"The run_id of the bulk job."

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"
+    },
+    "cached": {
+      "type": "integer"
+    },
+    "check_again_in_seconds": {
+      "description": "Do not poll sooner than this.",
+      "type": "integer"
+    },
+    "completed": {
+      "type": "integer"
+    },
+    "error": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "failed": {
+      "type": "integer"
+    },
+    "interrupted": {
+      "type": "integer"
+    },
+    "phase": {
+      "type": "string"
+    },
+    "quota": {
+      "description": "Videos not attempted because credits ran out.",
+      "type": "integer"
+    },
+    "remaining": {
+      "type": "integer"
+    },
+    "run_id": {
+      "type": "string"
+    },
+    "skipped": {
+      "description": "Videos without captions; never charged.",
+      "type": "integer"
+    },
+    "source": {
+      "properties": {
+        "title": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "type": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "url"
+      ],
+      "type": "object"
+    },
+    "status": {
+      "description": "running, completed or stopped.",
+      "type": "string"
+    },
+    "stopped": {
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "not_attempted": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "code"
+      ],
+      "type": "object"
+    },
+    "total": {
+      "type": "integer"
+    },
+    "videos_found": {
+      "description": "Null until a large channel has been listed.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "run_id",
+    "status",
+    "source",
+    "check_again_in_seconds",
+    "billing"
+  ],
+  "type": "object"
+}

AddedSep 18, 2026

TDQS

A3.8/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, closed-world), so the bar is lower. The description adds genuinely useful behavior: the poll-again semantics with the 0-means-finished termination signal, the meaning of each status bucket (skipped = no captions, quota = out of credits), and the cost note '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?

One dense sentence, front-loaded with the resource, then the returned fields and the polling hint. No wasted words, and the 'Free' cost note is placed last where it is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, enumerating return fields is somewhat redundant, but the operational detail that is NOT in the schema — the stop condition for polling and the credit-free cost — is included, so an agent has enough to call and loop this correctly.

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?

There is a single parameter (run_id) with 100% schema description coverage, so the schema already carries the parameter meaning. The description adds nothing about run_id syntax or where it comes from; baseline 3 applies when 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 names the specific resource ('bulk extraction job') and the exact information returned (progress status), so an agent can tell it apart from start_bulk_extract and list_bulk_results. It does not, however, explicitly contrast itself with those siblings.

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?

Usage is only implied through 'check_again_in_seconds, the suggested wait before the next check (0 means the job is finished)', which signals a polling pattern but never states when to call this versus list_bulk_results. No prerequisites or exclusions are given.

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?