Skip to main content
Glama

export_collection

Read-onlyIdempotent

Export all documents in a collection to a downloadable file. Preserve document hierarchy and content in outline-markdown, JSON, or HTML format.

Instructions

Exports all documents in a collection to a downloadable file.

IMPORTANT: This tool starts an asynchronous export operation which may take time to complete. The function returns information about the operation, including its status. When the operation is complete, the file can be downloaded or accessed via Outline's UI. The export preserves the document hierarchy and includes all document content and structure in the specified format.

Use this tool when you need to:

  • Create a backup of collection content

  • Share collection content outside of Outline

  • Convert collection content to other formats

  • Archive collection content for offline use

Args: collection_id: The collection ID to export format: Export format ("outline-markdown", "json", or "html")

Returns: Information about the export operation and how to access the file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYes
formatNooutline-markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Adds value beyond annotations by describing the async operation and file access method; annotations already declare readOnlyHint, destructiveHint, idempotentHint, and description aligns with those.

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?

Well-structured, concise, front-loaded, no unnecessary words.

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?

Covers async behavior, file access, and purpose; slightly vague about how to use the returned operation info, but adequate given presence of output schema.

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

Parameters2/5

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

Schema coverage is 0%, but description only briefly mentions parameters without adding meaning (e.g., does not list format options). Fails to compensate for missing schema descriptions.

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

Purpose5/5

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

Clearly states 'Exports all documents in a collection to a downloadable file,' distinguishing from siblings like export_document and export_all_collections.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Lists specific use cases (backup, share, convert, archive) and mentions asynchronous nature, but does not explicitly exclude use of alternatives or provide when-not-to-use guidance.

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/fastmcp-me/mcp-outline'

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