Skip to main content
Glama
Sign In
vish288

mcp-coda

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Coda Update Doc

coda_update_doc
Idempotent

Update an existing Coda doc's title or icon metadata without changing page content; returns updated doc metadata. Use for renaming or changing a doc icon.

Instructions

Update metadata for an existing Coda doc.

Updates the doc's title and/or icon. Does NOT update page content — use coda_update_page for that. Returns the updated doc metadata. This is an idempotent operation — calling with the same values produces the same result.

Input Schema

NameRequiredDescriptionDefault
titleNoNew title for the doc
doc_idYesThe ID of the doc to update
icon_nameNoNew icon name (e.g. 'rocket', 'star')

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

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

Annotations already declare this is a non-read-only, open-world, idempotent operation. The description adds useful behavioral context by stating what is mutated (title/icon only), what is not mutated (page content), and what is returned (updated doc metadata). It does repeat the idempotent hint, which adds no new information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and efficient, but the final sentence ('This is an idempotent operation — calling with the same values produces the same result') is largely redundant with the idempotentHint annotation and could be removed.

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?

For a mutation tool with no output schema, the description supplies what is needed: the scope of the update, the sibling alternative, and that it returns updated doc metadata. It does not describe auth requirements or returned metadata shape, but those are minor given the annotations and lack of output 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%, so title, icon_name, and doc_id are already documented. The description adds only the high-level mapping that title and/or icon are updated, which is useful but not meaningfully beyond the schema. Baseline 3 is appropriate.

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 ('Update metadata for an existing Coda doc') and immediately bounds the operation to title and icon only. It distinguishes itself from the sibling tool coda_update_page by explicitly saying it does not update page content.

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?

Gives clear when-to-use context ('Update metadata') and an explicit when-not with the correct alternative ('Does NOT update page content — use coda_update_page for that'). An agent can route between updating doc metadata and page content without inspecting schemas.

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