Skip to main content
Glama

List YouTube Playlists

postly_list_youtube_playlists
Read-onlyIdempotent

Lists one page of the selected connected YouTube channel playlists. Follow next_page_token until absent. Use the returned IDs in optional YouTube settings.playlist_ids.

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": {
      "workspace_id": "<workspace_id>",
      "channel_id": "<channel_id>"
    },
    "name": "postly_list_youtube_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYes
page_tokenNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
playlistsNo
next_page_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the call is paginated to one page at a time and must be looped until the token is absent. It doesn't mention rate limits or failure modes, but with annotations plus an output schema covering returns, the gap is small.

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?

Three short sentences, front-loaded with purpose, then pagination, then downstream use — no filler. The only blemish is the 'next_page_token' naming that doesn't match the 'page_token' schema field.

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

Completeness3/5

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

An output schema exists so return values needn't be described, and pagination behavior is covered. However, with 0% schema coverage the two required IDs remain semantically unexplained, and the relationship to postly_retry_youtube_playlists is left ambiguous, which is a real gap for a channel-scoped listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden, and it only partially does. It implies channel_id selects the channel and implies pagination, but workspace_id is never explained and the description calls the token 'next_page_token' while the schema parameter is 'page_token', which is a naming mismatch an agent has to reconcile.

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 gives a specific verb and resource: 'Lists one page of the selected connected YouTube channel playlists.' The channel scoping is stated, which tells an agent this is per-channel, not per-workspace, but it never names the closest sibling (postly_retry_youtube_playlists) so the agent must infer the boundary itself.

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 gives concrete operating guidance — 'Follow next_page_token until absent' — and says what the results are for ('Use the returned IDs in optional YouTube settings.playlist_ids'). It lacks any explicit when-not-to-use case or pointer to postly_retry_youtube_playlists, which is the one alternative an agent could easily confuse with this.

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