Skip to main content
Glama

List Coda Rows

coda_list_rows
Read-onlyIdempotent

List rows from a Coda table using filters, sorting, and pagination. Returns data in markdown or JSON format.

Instructions

List rows from a Coda table with optional filtering and sorting.

Args:

  • doc_id (string): The document ID

  • table_id (string): The table ID or name

  • query (string, optional): Filter rows — format: "columnId:value"

  • sort_by (string, optional): Sort column ID

  • limit (number): Max rows (default 25, max 500)

  • page_token (string, optional): Pagination token

  • value_format (string): 'simple' (default) or 'simpleWithArrays' or 'rich'

  • response_format: 'markdown' or 'json'

Returns: List of rows with their values keyed by column name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax items to return (1–500, default 25)
queryNoFilter rows: 'columnId:value'
doc_idYesCoda document ID
sort_byNoColumn ID to sort by
table_idYesTable ID or name
page_tokenNoToken for next page of results (from previous response)
value_formatNoValue format for row cellssimple
response_formatNoOutput format: 'markdown' for human-readable, 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, confirming safe read operation. The description adds useful behavioral details: pagination via page_token, default limit, and value_format options. 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?

The description is a concise docstring with a clear purpose sentence followed by a well-organized parameter list. Every sentence adds value, no redundancy, and it is appropriately front-loaded.

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 the annotations (readOnly, idempotent, openWorld), the description fully covers the tool's behavior: listing with filters, pagination, sorting, value format, and response format. No output schema exists, but the return description is sufficient.

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% with descriptions for all 8 parameters. The description adds extra meaning by explaining the query format (columnId:value) and clarifying response_format options (markdown vs json). This goes beyond the schema's basic descriptions, though not extensively.

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 lists rows from a Coda table with optional filtering and sorting. It distinctly identifies the resource (rows) and the action (list), and differentiates from siblings like coda_get_row (single row) and coda_upsert_rows (create/update).

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

Usage Guidelines3/5

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

The description implies usage for listing rows with filters but does not explicitly state when to use this tool versus alternatives like coda_get_row for single row retrieval or coda_upsert_rows for batch operations. No guidance on when not to use it.

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/thierryvm/coda-mcp-server'

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