Skip to main content
Glama

Update page

update_page
Idempotent

Update a wiki page's title, body, or properties. Body changes auto-snapshot a revision and support rich blocks like to-do lists, charts, and diagrams.

Instructions

Patch a page's title and/or body (editor+). A body change auto-snapshots a revision. tela renders a rich block palette beyond plain markdown — to-do list, pull quote, callout, collapsible, tabs, kanban board, stat grid, timeline, calendar, poll, chart, embed, mermaid diagram, image, file attachment, code block, equation, inline math, table, highlight, wikilink, footnote. Prefer these over walls of text; read the tela://authoring-guide resource (or this server's instructions) for exact syntax. When asked for a presentation, slides, a slide deck, or a talk (any phrasing) — not a prose doc — set the page property deck=true (and optionally variant=) and write the body as slides separated by --- using the tahta layouts; call the deck_authoring_guide tool (or read the tela://deck-authoring-guide resource) for the layouts, fields, components, and variants. When asked for a spreadsheet, a table of data with formulas/totals, a budget, a tracker, or any grid that computes — not a prose doc — set the page property sheet=true and write the body as Defter markdown (compact GFM tables + an optional ```defter-style block); call the sheet_authoring_guide tool (or read the tela://sheet-authoring-guide resource) for the format, formulas, and styling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYespage id to patch
bodyNonew markdown body (omit to leave unchanged)
propsNoreplace the whole properties bag (omit to leave unchanged); reserved keys are ignored
titleNonew title (omit to leave unchanged)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
Behavior5/5

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

Annotations already indicate idempotent and non-destructive behavior. The description adds valuable context: body changes trigger automatic revision snapshots, reserved keys are ignored, and the rich block palette availability. This goes beyond annotations to inform the agent of side effects and capabilities.

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

Conciseness3/5

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

The description is well-structured with a clear opening sentence, but it becomes verbose with extensive lists of block types and detailed instructions for decks and sheets. Some of this detail could be delegated to the referenced authoring guides, making the description more concise.

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?

Given the tool's complexity and the presence of an output schema (not shown but noted), the description covers key aspects: authentication (editor+), side effects (snapshots), content capabilities, and special use cases. Minor gaps exist, such as error handling or rate limits, but overall it provides sufficient context for an AI agent.

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 baseline is 3. The description adds significant value by explaining the 'body' parameter's special formatting options (tela blocks, decks, sheets) and the 'props' parameter's reserved key behavior. This enriches understanding beyond the schema's basic descriptions.

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 patches a page's title and/or body, with specific verb ('Patch') and resource ('page'). It distinguishes from creating a new page (different scope) and includes editor requirement, making purpose unambiguous. The context of slide decks and spreadsheets further clarifies use cases.

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

Usage Guidelines4/5

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

The description provides clear guidance on when to use this tool vs creating content types (slide decks, spreadsheets) with explicit instructions to set appropriate page properties. However, it does not directly compare to sibling tools like 'create_page' or 'patch_page' (if different), leaving some ambiguity about when to use alternatives.

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/zcag/tela'

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