Skip to main content
Glama
huiseo
by huiseo

list_collections

Retrieve all available collections from Outline wiki to organize and access documents efficiently for content management workflows.

Instructions

Get list of all collections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the list_collections tool. It calls the Outline API endpoint '/collections.list' to fetch collections and formats the results using formatCollections.
    async list_collections() {
      const { data } = await apiCall(() =>
        apiClient.post<OutlineCollection[]>('/collections.list')
      );
      return formatCollections(data || []);
    },
  • Zod schema definition for the list_collections tool input. It defines an empty object since the tool takes no parameters.
    export const listCollectionsSchema = z.object({});
  • src/lib/tools.ts:46-50 (registration)
    Registration of the 'list_collections' tool in the allTools array. It uses createTool to generate the MCP tool definition from the Zod schema, including name, description, and input schema.
    createTool(
      'list_collections',
      'Get list of all collections.',
      'list_collections'
    ),
  • Mapping of the list_collections tool name to its schema in the toolSchemas record, used by tool definitions.
    list_collections: listCollectionsSchema,
  • The toolSchemas map includes list_collections, linking the tool name to its input schema for use in MCP tool definitions.
    list_collections: listCollectionsSchema,
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get list' implies a read-only operation, but it doesn't specify details like pagination, sorting, or what fields are returned. For a tool with zero annotation coverage, this leaves the agent guessing about key behavioral aspects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence: 'Get list of all collections.' It's front-loaded with the core action, has zero wasted words, and efficiently communicates the tool's purpose without redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of listing operations in a system with many sibling tools, the description is incomplete. It lacks output details (no output schema), doesn't specify behavioral traits like filtering or ordering, and fails to differentiate from related tools. For a read operation in a rich environment, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, as there are none to explain. It appropriately focuses on the action, earning a high score for not introducing unnecessary complexity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get list of all collections' clearly states the verb ('Get') and resource ('collections'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_collection_structure' or 'export_all_collections', which also involve collections. The description is functional but lacks specificity about scope or format.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, such as whether it lists only active collections or includes archived ones. With many sibling tools like 'list_archived_documents' and 'list_trash', the lack of comparative guidance is a significant gap.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/huiseo/outline-wiki-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server