Skip to main content
Glama

ListCollections

List collections as a hierarchical tree for organizing assets. Supports filtering by parent path and depth. Each item has collection_kind: "static" (assets filed by hand) or "query" (a saved search whose contents are whatever its query matches when read; its query is returned).

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

Input Schema

NameRequiredDescriptionDefault
max_depthNoMaximum hierarchy depth to return (1-10). Default: 10
tenant_idNoTenant UUID (optional - auto-injected from API key auth)
parent_pathNoOptional filter to list only descendants of this path (ltree format, e.g., "projects.nike")
include_asset_countsNoInclude asset count per collection. Default: true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / max_depth / default
      Previous value: -5New value: +10
    • changedInput schema / properties / max_depth / description
      Previous value: -"Maximum hierarchy depth to return (1-5). Default: 5"New value: +"Maximum hierarchy depth to return (1-10). Default: 10"
    • changedInput schema / properties / max_depth / maximum
      Previous value: -5New value: +10
  2. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description holds the full burden. It does add meaningful semantics — that "query" collections are saved searches whose contents are whatever the query matches at read time, and that the query is returned — but it says nothing about permissions/tenant scoping, whether the tree is truncated by max_depth, ordering, or result-size limits for a potentially large hierarchical listing.

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 sentences, front-loaded with purpose, then filters, then item semantics; each sentence carries new information with no filler. The final sentence is dense but it resolves a real ambiguity about what a "query" collection returns.

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 read-only listing tool with no annotations and no output schema, the definition covers purpose, filterable dimensions, and the meaning of the returned kind field, which is most of what an agent needs. Minor gaps remain around ordering, truncation, and volume limits of a tree listing.

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%, so all four parameters are already documented in the input schema. The description only restates that parent path and depth filtering are supported and adds no format or interaction details (e.g., how max_depth truncation behaves) 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?

The first sentence gives a specific verb and resource ("List collections") plus the shape of the result ("hierarchical tree for organizing assets"), which is more than a restatement of the name. It does not name a sibling such as GetCollectionAssets to contrast with, so it stops short of full 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 only implied: the mention of scene-appropriate filtering (parent path, depth) suggests browsing or scoping a subtree, and the collection_kind explanation hints at when "query" results may be unstable. There is no explicit when-to-use, when-not-to-use, or comparison against sibling listing/asset tools.

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