Skip to main content
Glama
huiseo

Outline Wiki MCP Server

by huiseo

export_all_collections

Export all collections from Outline wiki in Outline Markdown or JSON format for backup, migration, or external use.

Instructions

Export all collections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNooutline-markdown

Implementation Reference

  • The async handler function that implements the core logic of the export_all_collections tool by calling the Outline API endpoint '/collections.export_all'.
    async export_all_collections(args: ExportAllCollectionsInput) {
      const { data } = await apiCall(() =>
        apiClient.post<unknown>('/collections.export_all', { format: args.format })
      );
      return {
        success: true,
        format: args.format,
        fileOperation: data,
        message: MESSAGES.COLLECTION_EXPORT_ALL_STARTED,
      };
    },
  • Zod input schema for the export_all_collections tool, defining the 'format' parameter.
    export const exportAllCollectionsSchema = z.object({ format: exportFormat });
  • MCP tool registration defining the name, description, and linking to the Zod schema for export_all_collections.
    createTool(
      'export_all_collections',
      'Export all collections.',
      'export_all_collections'
    ),
  • Registration of the export_all_collections schema in the central toolSchemas object.
    export_all_collections: exportAllCollectionsSchema,
  • Shared schema fragment for export format used by export_all_collections and other export tools.
    const exportFormat = z.enum(['outline-markdown', 'json']).default('outline-markdown');
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 action without behavioral details. It doesn't disclose whether this is a read-only operation, if it requires specific permissions, what the output looks like (file, data structure), or any side effects like rate limits or system impact.

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?

Extremely concise with just three words, front-loaded with the core action. Every word earns its place by specifying the verb, scope, and target without any fluff or redundant information.

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 tool that presumably performs a bulk export operation with no annotations and no output schema, the description is insufficient. It doesn't explain what 'export' entails (e.g., file download, data return), scope limitations, or error handling, leaving significant gaps for an agent to understand the tool's behavior.

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%, but the single parameter 'format' has an enum with clear options. The description adds no parameter semantics beyond what the schema provides, but with only one optional parameter and enum values, the baseline is adequate. No additional context about format implications is given.

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 'Export all collections' clearly states the action (export) and target (all collections), but it's vague about what 'export' means in practice. It distinguishes from sibling 'export_collection' by specifying 'all' vs. single collection, but doesn't clarify the scope or output format beyond the schema's enum.

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?

No guidance on when to use this tool versus alternatives like 'export_collection' for single collections or other export-related tools. The description implies bulk export but doesn't specify prerequisites, timing, or constraints that would help an agent choose appropriately.

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