Skip to main content
Glama

Create Document

create_document

Create a new text document or folder within a Scrivener project binder. Set initial content and parent folder, or add at the top level.

Instructions

Create a new text document or folder in the binder and return its new id. Optionally set the initial body content and the parent folder; if no parent is given the item is added at the top level. Each call creates a distinct item (not idempotent). Use write_document to change content afterward. Requires an open project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoWrite even if the project appears open in Scrivener. Default false, which refuses the write to protect against your changes being overwritten by Scrivener on save.
titleYesTitle for the new document or folder. Truncated to 255 characters.
contentNoDocument body as plain text. May be empty.
parentIdNoUUID of a binder folder, as returned by get_structure.
documentTypeNoWhether to create a "Text" document (default) or a "Folder".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentIdYesScrivener UUID of the newly created document or folder.
Behavior4/5

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

Discloses non-idempotency (matching annotations) and requirement for open project (beyond annotations). No contradictions with annotations.

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?

Three sentences, front-loaded with main action, no wasted 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 creation, optional parent, non-idempotency, and alternative tool. Output schema handles return values. Could mention default documentType, but not essential.

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%, so description need not repeat schema. Adds context about parent behavior ('top level') but does not elaborate on force or documentType defaults. Value added is modest.

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?

The description clearly states the tool creates a text document or folder, returns a new ID, and optionally sets content and parent. It distinguishes itself from write_document for subsequent edits.

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?

Explicitly mentions requires an open project and directs to write_document for content changes. Could be more explicit about when not to use, but the main alternative is provided.

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/writerslogic/scrivener-mcp'

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