Skip to main content
Glama

batch_create_documents

DestructiveIdempotent

Create multiple documents in one batch operation. Use for bulk importing content or setting up document structures.

Instructions

Creates multiple documents in a single batch operation.

This tool processes each creation sequentially, continuing even if individual operations fail. Rate limiting is handled automatically.

Each document dictionary should contain:

  • title (required): Document title

  • collection_id (required): Collection ID to create in

  • text (optional): Markdown content

  • parent_document_id (optional): Parent document for nesting

  • publish (optional): Whether to publish immediately (default: True)

Use this tool when you need to:

  • Create multiple documents at once

  • Bulk import content into collections

  • Set up document structures efficiently

Note: For Mermaid diagrams, use mermaidjs (not mermaid) as the code fence language identifier for proper rendering.

Recommended batch size: 10-50 documents per operation

Args: documents: List of document specifications, each containing title, collection_id, and optional text, parent_document_id, and publish fields

Returns: Summary of batch operation with created document IDs and success/failure details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses sequential processing with continuation on failure and automatic rate limiting. Annotations indicate destructiveHint and idempotentHint; description adds operational details without contradiction.

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?

Well-structured with clear sections: purpose, behavior, parameter details, usage scenarios. Slightly verbose but each sentence adds value. Could be tightened slightly.

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 all critical aspects: purpose, parameters, behavior, usage, and a rendering note. Although no output schema is provided, the description mentions a summary with IDs and success/failure, which is sufficient context.

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

Parameters5/5

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

With 0% schema coverage, the description fully compensates by detailing all expected fields (title, collection_id, text, parent_document_id, publish) and their required/optional status, providing essential guidance beyond the open-ended 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 description clearly states the tool creates multiple documents in a single batch operation. It distinguishes from single document creation and other batch operations by specifying bulk creation, but does not explicitly contrast with sibling batch tools.

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?

Provides explicit use cases: creating multiple documents, bulk import, setting up structures. Includes a notable tip about Mermaid code fences. Does not explicitly exclude single-document use, but implication is clear.

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