get_creditsCheck the remaining credit balance of the API key. Free. Use it when the user asks how many credits are left, or before submit_transcripts_job to confirm a large batch fits the balance (the batch charges 1 credit per video on submit).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| credits | No | ||
| metered | No | ||
| user_id | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this read-only, and the description adds that it is 'Free,' which is a useful operational trait beyond the schema. It also clarifies the billing behavior of the related submit_transcripts_job tool, adding context that helps the agent reason about the overall workflow.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is brief and front-loaded with the core purpose, followed by a single useful usage directive. Every sentence adds value; there is no filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With zero parameters, an output schema present, and clear use-case guidance including a cancellation-around submit_transcripts_job, nothing essential is missing. The description fully equips the agent to select and call this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there is nothing to describe. Schema coverage is 100% and the description adds no redundant parameter detail, which aligns with the baseline for 0-parameter tools.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description starts with a specific action verb ('Check') and a clear resource ('remaining credit balance of the API key'), making the tool's purpose unambiguous. It is clearly distinct from all sibling tools, none of which concern credit balances.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use it: 'when the user asks how many credits are left' and gives a concrete workflow, 'before submit_transcripts_job to confirm a large batch fits the balance.' This is actionable, context-rich routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target a distinct resource and action: search, list, metadata, transcript, job lifecycle, and credits. The get_transcripts_job / get_transcripts_result / get_transcripts_results trio is easy to blur at first glance, but the descriptions clearly differentiate job status, one result, and paged results.
The set mostly follows a predictable verb_noun pattern: get_, list_, search_, submit_, cancel_. The main deviation is latest_channel_videos, which uses an adjective instead of a verb, and the result/results pair is mildly confusing, but overall naming is coherent and easy to navigate.
14 tools is well within the sweet spot for a server with this scope. Each tool serves a clear niche: video lookup, metadata, single transcripts, batch jobs, and search are all represented without unnecessary or redundant tools.
The server provides full coverage of the transcript and search workflow: search YouTube, list channel/playlist videos, fetch or batch-fetch transcripts, check job progress/credits, and read results. There are no obvious missing operations that would force an agent into a dead end.