Skip to main content
Glama

BulkTranscripts YouTube

Check a bulk job

get_bulk_status
Read-onlyIdempotent

Progress of a job started with start_bulk_extract: status (running, completed, stopped, failed), total, completed, failed, skipped (no captions), quota (not attempted for lack of credits), remaining, and check_again_in_seconds. Free. Wait at least check_again_in_seconds between polls; 0 means the job is finished.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYesThe run_id from start_bulk_extract.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
phaseNo
quotaNoVideos not attempted because credits ran out.
totalNo
cachedNo
failedNo
run_idYes
sourceYes
statusYesrunning, completed or stopped.
billingYes
skippedNoVideos without captions; never charged.
stoppedNo
completedNo
remainingNo
interruptedNo
videos_foundNoNull until a large channel has been listed.
check_again_in_secondsYesDo not poll sooner than this.

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"
      +    },
      +    "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"
      +}
  2. Added

TDQS

A4.1/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), and the description adds real behavioral value beyond them: the polling cadence constraint, the meaning of check_again_in_seconds=0, and that the call is free. It does not discuss error behavior for an unknown run_id, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with the core purpose front-loaded and no filler. The middle field list is a long run-on, though it is information-bearing rather than padding.

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?

Given an output schema exists, the return-field enumeration is partly redundant, but the polling rule and the quota/no-captions semantics make the definition self-sufficient for correct invocation. Nothing critical an agent needs 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?

There is a single run_id parameter with 100% schema description coverage, and the schema already states it comes from start_bulk_extract. The description adds no format or validation detail beyond that, so the baseline 3 applies.

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 first clause names the specific resource (progress of a job from start_bulk_extract) and enumerates the status values, so an agent can immediately distinguish it from start_bulk_extract and list_bulk_results.

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 ties itself to the start_bulk_extract workflow and gives an explicit polling rule ('Wait at least check_again_in_seconds between polls; 0 means the job is finished'), which is clear usage context. It never names list_bulk_results as the follow-up for fetching results, so the alternative-route guidance is incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources