Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get YouTube playlist

youtube_playlist_get
Read-onlyIdempotent

Fetch a YouTube playlist by ID or URL to retrieve its details and videos, with cursor-based pagination for long lists.

Instructions

Get a YouTube playlist by playlist id. Requires playlistId.

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": {
      "playlistId": "<playlistId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "youtube_playlist_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor from `data.page.nextCursor` of a previous response. Omit for the first page. Send the same `playlistId` on every page.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
playlistIdYesYouTube playlist id, or a YouTube playlist URL (the `list` query value is used when present).
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety and idempotency are covered without prose. The description adds nothing beyond that, but it also contradicts nothing, and for a simple single-resource read the annotation set is doing nearly all the work. The absence of any note on quota cost or return shape keeps it from 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 short sentences, front-loaded with the verb and resource — an agent can act immediately. The second sentence ('Requires `playlistId`') is redundant with the schema's required list, so it does not fully earn its place, but there is no padding or preamble.

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?

With 5 parameters (3 required, including platform-injected context/llm_model/conversation_id) and no output schema, the description carries the burden of explaining what comes back, and it does not — no mention of playlist metadata fields, item counts, or that results are paged via `cursor`. It is adequate to select and invoke the tool but under-informs on outcome.

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 the baseline of 3 applies. The description repeats only `playlistId` and omits the schema's useful detail that a full playlist URL is accepted and that `list` is extracted, plus nothing about the pagination cursor semantics. No added meaning beyond the schema.

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: 'Get a YouTube playlist by playlist id.' That is unambiguous and clearly distinct from track-, video-, or channel-level siblings. It stops short of naming what it returns (metadata vs. items) or contrasting with a playlist-tracks-style sibling, so not a 5.

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 by 'by playlist id' — the agent infers this is the tool for a single known playlist. There is no guidance on when to prefer it over search or a playlist-tracks listing, and no mention of pagination behavior in-text despite a `cursor` param existing. The second sentence merely restates the required field the schema already marks required.

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

Deploy Server

Other Tools