Skip to main content
Glama
zcag

tela

by zcag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Update page

update_page
Idempotent

Patch a tela wiki page's title, body, props, or draft status; body edits auto-snapshot a revision, and base_version stops overwriting concurrent changes.

Instructions

Patch a page's title, body, props and/or draft status (editor+). A body change auto-snapshots a revision. Pass base_version (from get_page) to refuse the write if someone edited the page since you read it. 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. After writing, call lint_page — the reader silently drops raw HTML and unwraps unrecognized blocks, which you cannot see from the markdown. 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

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)
statusNo'draft' or 'published' (omit to leave unchanged). Publishing a draft makes it eligible for public spaces and share links
base_versionNooptional: the page version you last read (get_page returns it). If the page has changed since, the write is refused with version_conflict instead of overwriting that edit; re-read and reapply. Omit for last-write-wins

Output Schema

NameRequiredDescriptionDefault
lintNo
pageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.11.0
    • addedInput schema / properties / base_version
      Added value: +{
+  "description": "optional: the page version you last read (get_page returns it). If the page has changed since, the write is refused with version_conflict instead of overwriting that edit; re-read and reapply. Omit for last-write-wins",
+  "type": [
+    "null",
+    "integer"
+  ]
+}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "'draft' or 'published' (omit to leave unchanged). Publishing a draft makes it eligible for public spaces and share links",
+  "type": [
+    "null",
+    "string"
+  ]
+}
    • addedOutput schema / properties / lint
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / page / properties / epistemic / properties / summary_stale
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / page / properties / sections / items / properties / in_quote
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / page / properties / status
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / page / properties / version
      Added value: +{
+  "type": "integer"
+}
    • changedOutput schema / properties / page / required
      Previous value: -[
-  "id",
-  "space_id",
-  "parent_id",
-  "title",
-  "body",
-  "position",
-  "created_at",
-  "updated_at",
-  "url"
-]New value: +[
+  "id",
+  "space_id",
+  "parent_id",
+  "title",
+  "body",
+  "position",
+  "created_at",
+  "updated_at",
+  "version",
+  "status",
+  "url"
+]
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark this as non-readOnly, idempotent, non-destructive, but the description adds behavior beyond them: a body change auto-snapshots a revision, base_version triggers a version_conflict refusal rather than overwriting, editor+ permission is required, and the reader silently drops raw HTML / unwraps unrecognized blocks. These are concrete consequences an agent needs before invoking.

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 core action and the highest-value guidance (revision snapshot, base_version conflict, lint_page) are front-loaded, which is good. But the long enumerations of block palette items and the deck/sheet instructions are verbose, and the description itself points to the tela:// resources for the details, so this content partially duplicates what those resources hold. It is serviceable but not tight.

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?

An output schema exists, so return values need not be explained. Given a 6-parameter, nested-object mutation tool, the description covers permissions, idempotency/conflict handling, post-write validation, and the special deck/sheet modes. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema by tying base_version to get_page as the source of the value, and by revealing that props carries reserved keys like deck and sheet that switch authoring modes. That is genuine parameter semantics not present in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb + resource + field set: 'Patch a page's title, body, props and/or draft status (editor+).' That is unambiguous about what the tool does. However, the sibling list contains patch_page, and the description never distinguishes update_page from it, so an agent cannot cleanly route between the two from this text alone.

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?

The description gives explicit when-to-use routing: use base_version to detect concurrent edits, call lint_page after writing, and set deck=true vs sheet=true depending on whether the request is for a presentation/deck vs a spreadsheet/grid. It also names the alternatives (deck_authoring_guide, sheet_authoring_guide, the tela:// resources) and the condition that selects each. This is exactly the kind of decision guidance the dimension rewards.

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