Skip to main content
Glama

Export Project To File

export_project
Read-onlyIdempotent

Export a Scrivener project to publishing or interchange formats. Text formats (Markdown, HTML, JSON) return content inline; binary formats (DOCX, EPUB, PDF) save to disk.

Instructions

Export the whole project to a publishing/interchange format. Markdown, HTML, and JSON are returned inline; DOCX (agent/editor submission), EPUB (e-readers), and PDF (print/review) are written to a file on disk and the path is returned. Use this to produce a deliverable file; use compile_documents when you want the compiled text back in the response rather than written to disk. Requires an open project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatYesTarget file format. Text formats (markdown, html, json) return their content inline; binary formats (docx, epub, pdf) are written to a file and return its path.
optionsNoOptional format-specific export options (e.g. metadata, styling).
outputPathNoAbsolute or project-relative path to write the exported file. Omit to use a default location (the working directory, named after the project title). Required in effect only if you want a specific location for docx/epub/pdf.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPath of the written file (binary formats: docx, epub, pdf).
bytesNoSize of the written file in bytes (binary formats only).
formatYesFormat the project was exported to (markdown, html, json, docx, epub, or pdf).
contentNoThe exported document content (text formats only).
metadataYesExport metadata: exportDate, format, and documentCount (number of documents exported).
Behavior5/5

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

Beyond annotations (readOnly, idempotent), description explains inline vs file output behavior for each format, and that file path is returned. Adds context about file writing not being destructive to project.

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 purpose, then details, then usage guidance. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists, description covers all necessary context: what, formats, return mechanism, sibling differentiation, prerequisite. Complete for this tool.

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

Parameters4/5

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

Schema coverage is 100%, but description adds nuance: explains that outputPath only needed for specific location, and options are format-specific. Slightly redundant but helpful.

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?

Explicitly states it exports the whole project to publishing/interchange formats, lists specific formats, and distinguishes from the sibling tool compile_documents. The verb 'export' and resource 'project' are clear.

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

Usage Guidelines5/5

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

Provides clear guidance: use for deliverable files, use compile_documents for inline compiled text. Also notes prerequisite 'requires an open project'.

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