Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda Get Export Status

coda_get_export_status
Read-onlyIdempotent

Check the status of a Coda page export and get the download link when complete. Poll every 2 seconds; if failed, the error explains why.

Instructions

Check a page export started by coda_export_page.

Pass the id from coda_export_page as request_id. status is inProgress, failed or complete. When complete, downloadLink holds the exported file; the link expires after a short time — call this tool again for a fresh one. When failed, error says why. Poll every 2 s for up to 30 s (same cadence as coda_get_mutation_status). The request itself expires: 404/410 means start a new export.

Input Schema

NameRequiredDescriptionDefault
doc_idYesThe doc ID containing the page
request_idYesExport request ID returned by coda_export_page
page_id_or_nameYesPage ID or name that was exported

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. Addedv0.9.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, idempotent, openWorld); the description adds substantial behavior beyond that: the terminal states inProgress/failed/complete, that downloadLink expires and must be re-fetched, that error explains failures, and that the request itself expires. This is exactly the added context annotations cannot supply.

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?

Front-loaded with purpose and the request_id mapping, then the state machine, then the expiry caveat. Every sentence carries operational information; nothing is redundant with the schema or annotations.

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, so the description correctly documents the returned fields (status, downloadLink, error) and their lifecycle. Combined with the polling and expiry guidance, an agent has everything needed to call and interpret 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%, so the baseline is 3, but the description adds real value the schema cannot: it clarifies the naming mismatch that the `id` returned by coda_export_page must be passed as request_id. That resolves a genuine ambiguity for the agent.

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 precise verb+resource ('Check a page export') and immediately anchors it to the sibling that creates the request ('started by coda_export_page'). An agent can distinguish this from the other ~50 coda_* tools without opening the 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 defines when to call (after coda_export_page), the polling policy (every 2 s up to 30 s), the same cadence as coda_get_mutation_status, and the recovery path when 404/410 is returned (start a new export). Both when-to-use and failure handling are covered.

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