Skip to main content
Glama

create_document

Create a long-form document with rich text content by providing a title and Quill Delta JSON. Use for essays, articles, and any rich-text documents.

Instructions

Create a long-form document

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formYesDocument form type enum. Use 1 for LONG_FORM (Quill-editor-backed documents — the standard for essays, articles, and any rich-text content). 0 = SHORT_FORM (AI templates, not used by these skills).
titleYesDocument title shown in the editor and the document list. For AI-writer skills, use the essay/article title from the originating show_article tool call.
parentNoOptional parent document id for creating a sub-document. Not used by AI-writer skills in v1.
contentYesQuill Delta JSON representing the document body. Contains an `ops` array of operations. Each op is a dict with `insert` (string or embed object) and optional `attributes` (formatting like bold, italic, header, list, link, code-block, blockquote). For markdown-sourced content, call `markdown_to_quill_delta` to produce a compliant Delta before passing to this field.
payloadNoOptional document metadata. Can be left empty ({}). Supported fields: description, tone, keywords, voice_id, output. Used for AI template context — not required for skill-generated content.
Behavior2/5

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

With no annotations, the description carries full disclosure burden. It only says 'Create,' implying mutation, but omits details on permissions, side effects, return values, or behavior regarding existing documents. Very sparse.

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

Conciseness2/5

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

The description is a single short sentence, which is concise but lacks key information. It does not front-load important context or structure for quick understanding.

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 5 parameters with nested objects and no output schema, the description should explain return values and typical usage. It does not address these, leaving the agent without sufficient operational context.

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 coverage is 100% and each parameter already has a detailed description. The tool description adds no extra meaning beyond 'Create a long-form document.' Baseline 3 is appropriate.

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 states 'Create a long-form document,' which clearly identifies the verb and the resource. It distinguishes from sibling tools like create_context_document or create_social_media_post by specifying 'long-form,' but does not explicitly differentiate between document subtypes.

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 create_context_document or create_social_media_post. The description lacks any context about prerequisites, typical scenarios, or when not to use it.

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/celeryhq/simplified-mcp-server'

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