Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda List Pages

coda_list_pages
Read-onlyIdempotent

Retrieve all pages in a Coda doc to get their metadata (name, ID, parent, icon) in tree order. Use the returned IDs for subsequent page operations.

Instructions

List all pages in a Coda doc.

Returns page metadata including name, ID, parent page, and icon. Pages are returned in their tree order. Does NOT return page content — use coda_get_page_content for that. Use the returned page IDs (not names) for all subsequent page operations.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of pages to return (1-200)
cursorNoPagination cursor from a previous response
doc_idYesThe doc ID containing the pages

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.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), and the description adds genuinely new behavioral facts: pages come back in tree order, the response contains name/ID/parent/icon metadata, and content is deliberately excluded. It stops short of describing pagination behavior (cursor semantics, what happens when more pages exist than limit), so it is strong but not exhaustive.

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 sentences, front-loaded with the core action and the negative scope, then the return shape, then the downstream ID rule. No filler and no repetition of the title.

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?

With no output schema, the description usefully enumerates the returned metadata fields and ordering, which is what an agent needs to consume the result. The only remaining gap is pagination behavior, though the cursor parameter is self-documented in the schema.

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 every parameter (limit, cursor, doc_id) is already documented inline, including the 1-200 bound and the default of 50. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

Opens with a specific verb+resource ('List all pages in a Coda doc') and immediately scopes it against the nearest sibling by stating it does NOT return page content and naming coda_get_page_content. An agent can distinguish it from coda_get_page, coda_list_docs, and coda_get_page_content without opening any 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 names the alternative (coda_get_page_content) and the condition that selects it, and adds a follow-on usage rule ('Use the returned page IDs (not names) for all subsequent page operations'), which is exactly the kind of when-to-use guidance an agent needs for chained calls.

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