Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda Export Page

coda_export_page
Read-only

Export a Coda page's full content, including embedded images. For large pages, start an async export and get an ID to check status later.

Instructions

Export a page's content, initiating an async export if needed.

Starts an export job and returns the export status. For small pages, the content may be returned immediately. For large pages, call coda_get_export_status with the returned id. Prefer coda_get_page_content for quick reads — use this only when you need a full export with embedded images resolved.

Input Schema

NameRequiredDescriptionDefault
doc_idYesThe doc ID containing the page
output_formatNoExport formatmarkdown
page_id_or_nameYesPage ID or name to export

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.1
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.4.14

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description must carry the operational detail — and it does, disclosing the async job semantics, that small pages may return content inline, and that large pages yield an id requiring a status poll. It stops short of discussing export quotas, latency, or whether repeated exports are deduplicated, keeping it just below a 5.

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 short paragraphs, front-loaded with the operation and its async nature, then the polling path, then the routing advice as a closing preference. Every sentence carries distinct information with no restatement of the name or title.

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?

There is no output schema, yet the description explains what comes back in both branches (immediate content vs. an id for polling) and names the sibling that consumes that id. Combined with the schema's full parameter coverage, an agent has everything needed to call this tool and handle its result correctly.

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 description coverage is 100% and all three parameters (doc_id, page_id_or_name, output_format) are documented in the schema itself, so the baseline of 3 applies. The description hints at format relevance via 'embedded images resolved' but adds no format syntax, defaults, or page-name resolution rules beyond the schema.

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?

States a specific verb and resource: 'Export a page's content, initiating an async export if needed.' It immediately differentiates itself from the closest sibling by framing the operation as a heavier full export rather than a quick read, so an agent can distinguish it from coda_get_page_content without opening either schema.

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?

Explicitly routes the agent: 'Prefer coda_get_page_content for quick reads — use this only when you need a full export with embedded images resolved.' It also names the follow-up tool, coda_get_export_status, and states the condition that triggers it (large pages), giving when-to-use, when-not-to-use, and the alternative in a single paragraph.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools