Skip to main content
Glama

list_playbooks

Read-onlyIdempotent

List playbooks in the user's Ballet workspace. Use when the user wants to find, choose, or inspect an existing automation before running or editing it. Optionally filter by collectionId.

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

Input Schema

NameRequiredDescriptionDefault
collectionIdNoFilter by collection ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful scoping (results are limited to the user's workspace) but says nothing about pagination, ordering, or what fields a playbook entry contains, which it could have done given no output schema exists.

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 the core action and followed by usage context and the optional filter. Every sentence carries information; nothing is padded or redundant.

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?

For a simple read-only list tool with one optional parameter and full annotation coverage, the description supplies enough to invoke it correctly. The main residual gaps are return shape and pagination behavior, which are less critical since this is a straightforward listing operation.

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 single collectionId parameter is already documented in the schema. The description only restates it as an optional filter, adding no syntax, format, or behavior detail (such as whether unknown IDs error or return an empty list) beyond structured data.

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 ("List playbooks") plus scope ("in the user's Ballet workspace"), so an agent can distinguish it from create_playbook and other mutations without opening the schema. It stops short of explicitly contrasting with sibling list_* tools, so it is clear but not maximally differentiated.

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 states a concrete use case: when the user wants to find, choose, or inspect an existing automation before running or editing it. That covers the positive trigger well, but there is no explicit when-not guidance or named alternative (for example, when to prefer a search or get-by-id call instead).

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