Skip to main content
Glama

youtube_list_videos

Read-onlyIdempotent

List videos on the connected YouTube channel. Returns id, title, published_at, view_count. Paginate via page_token.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "youtube_list_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoWhich connected YouTube channel to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.
page_tokenNoPagination cursor returned in a previous call's `next_page_token`. Omit for the first page.
max_resultsNoPage size, 1-50. Default 25.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Which connected YouTube channel to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds useful context beyond them: the exact return fields (id, title, published_at, view_count) and the pagination model. It stops short of describing ordering, default page contents, or what happens on empty results.

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?

Three short sentences with zero filler, front-loading the action first, then the return shape, then pagination. Every sentence carries information an agent can use.

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 no output schema, the description correctly compensates by naming the returned fields, and it covers pagination. The remaining gap is minor: sort order and whether all uploads versus a filtered subset are returned is unstated.

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 four parameters (including the multi-channel refusal behavior for account_id and the workspace override) are already documented. The description's mention of page_token only restates the schema, adding no new meaning.

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?

States a specific verb and resource ('List videos on the connected YouTube channel') with a clear scope. It does not, however, distinguish itself from closely related siblings such as youtube_video_query, so an agent must still infer which listing/query tool to pick.

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: the description makes clear this is for enumerating a channel's videos, but gives no when-to-use/when-not guidance, no prerequisites, and no pointer to an alternative for filtered queries. 'Paginate via page_token' is the only procedural hint.

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.