Skip to main content
Glama

get_all_playlists

Read-onlyIdempotent

Get all playlists for given workspace

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": "get_all_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idNoGumlet video workspace ID. Preferred. Provide one of `workspace_id` or the deprecated aliases below (same ID).
collection_idNoDeprecated. Use `workspace_id` instead. Still accepted for backwards compatibility.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / collection_id / description
      Previous value: -"Workspace ID"New value: +"Deprecated. Use `workspace_id` instead. Still accepted for backwards compatibility."
    • addedInput schema / properties / workspace_id
      Added value: +{
      +  "description": "Gumlet video workspace ID. Preferred. Provide one of `workspace_id` or the deprecated aliases below (same ID).",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "collection_id"
      -]New value: +[]
  2. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "collection_id"
      +]
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered without the description. Beyond that, the description adds nothing: no pagination behavior, no result-set size expectations, no note that the workspace filter is optional and what an unfiltered call returns.

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?

A single front-loaded sentence with no filler, which is the right shape for a simple list tool. It is arguably terse to the point of under-specification, but nothing in it is wasted.

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 an output schema present, return values need no explanation, and annotations cover the safety profile. However, for a tool with zero required parameters, the description never says what happens when no workspace is supplied, which is the main ambiguity an agent would face.

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%, including the explicit note that collection_id is a deprecated alias of workspace_id, so the schema carries the parameter burden. The description's 'for given workspace' loosely gestures at workspace_id but adds no syntax or fallback behavior beyond the schema; baseline 3 applies.

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 ('Get all playlists') plus a scope ('for given workspace'), so the operation is unambiguous. It does not differentiate itself from siblings such as get_playlist_assets or list_profiles, nor does it clarify that it is a workspace-scoped enumeration versus the single-playlist read tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of alternatives (e.g. get_playlist_assets for contents of one playlist), and no statement about prerequisites or behavior when workspace_id is omitted. The agent must infer everything from the name and schema.

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