Skip to main content
Glama

List collections

list_collections
Read-onlyIdempotent

List your collections, sound boards, or both. Free accounts can hold 1 collection and 1 sound board. Pro accounts can hold up to 1,000 of each; a lapsed Pro account can still view everything but only one collection and one sound board are editable. A sound board is a collection with kind "board".

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_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhich kind to list. Defaults to collection; use board for sound boards or all for both.
include_archivedNoAlso list archived collections. They are hidden by default but still count toward the cap.

Output Schema

NameRequiredDescriptionDefault
collectionsYes
entitlementsYes
archived_countYesArchived collections that still count toward the plan cap, even when they are hidden from the list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: free/Pro capacity limits, that a lapsed Pro account can view everything but edit only one of each, and that archived items are hidden but still count toward the cap.

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?

Four short sentences, front-loaded with the action and followed by the account-tier and archival nuances; nothing is padded or repeated. The account-cap sentences are slightly tangential to the call itself but earn their place as behavioral context.

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 rich annotations, 100% schema coverage, and an output schema handling return values, the description covers what remains: capacity limits and archived-visibility semantics. It stops short of mentioning result-set size limits or pagination, but that is minor given the structured fields.

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 coverage is 100% and the kind enum is already documented with its default and allowed values, so the schema does the heavy lifting. The description's definition of a board as a collection with kind "board" adds modest conceptual clarity but no syntax, format, or edge-case detail 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: "List your collections, sound boards, or both," and clarifies that a sound board is just a collection with kind "board." It never names the closest sibling (search_collections) to route the agent away from it, so it falls short of full sibling differentiation.

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 implied by the verb "list" and by the account-cap context, which hints at when viewing vs editing matters, but there is no explicit when-to-use or when-not-to-use guidance relative to search_collections or list_filter_values.

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