Skip to main content
Glama
huiseo

Outline Wiki MCP Server

by huiseo

create_collection

Create a new collection in Outline Wiki to organize documents by name, description, and color for better content management.

Instructions

Create a new collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
descriptionNo
colorNo

Implementation Reference

  • The main execution logic for the create_collection tool. It validates access, builds the payload from input args, calls the API to create the collection, and returns the result with a success message.
    async create_collection(args: CreateCollectionInput) {
      checkAccess(config, 'create_collection');
    
      const payload: Record<string, unknown> = { name: args.name };
      if (args.description) payload.description = args.description;
      if (args.color) payload.color = args.color;
    
      const { data } = await apiCall(() =>
        apiClient.post<OutlineCollection>('/collections.create', payload)
      );
      return colResult(data, MESSAGES.COLLECTION_CREATED);
    },
  • Zod schema defining the input parameters for the create_collection tool: required name, optional description and color.
    export const createCollectionSchema = z.object({
      name: z.string().min(1, 'Name is required'),
      description: z.string().optional(),
      color: hexColor.optional(),
    });
  • Registers the create_collection tool in the allTools array by calling createTool with name, description, and schema key, converting Zod schema to JSON schema for MCP.
    createTool(
      'create_collection',
      'Create a new collection.',
      'create_collection'
    ),
  • Includes the createCollectionHandlers (containing create_collection) into the combined ToolHandlers object in createAllHandlers.
    ...createCollectionHandlers(ctx),
    ...createCommentHandlers(ctx),
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral aspects like required permissions, whether creation is idempotent, what happens on duplicate names, or what the response contains. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise at three words, front-loading the essential action and resource with zero wasted words. It efficiently communicates the core purpose without unnecessary elaboration.

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?

For a creation tool with 3 parameters, no annotations, and no output schema, the description is insufficient. It doesn't cover what a collection represents in this system, how it relates to other resources, or what to expect upon creation. More context is needed given the complexity implied by sibling tools.

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 0%, so the description must compensate but adds no parameter information beyond the tool name implying a 'collection' resource. It doesn't explain what 'name', 'description', or 'color' parameters mean or their significance. Baseline is 3 since the schema fully defines parameters, but the description adds minimal value.

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 clearly states the action ('Create') and resource ('a new collection'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'batch_create_documents' or specify what distinguishes a collection from other resources in this system.

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 like 'batch_create_documents' or 'update_collection', nor does it mention prerequisites or typical use cases. It's a bare statement of function without context.

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-smart-mcp'

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