Skip to main content
Glama

Create page

create_page

Create a page in a space using markdown. Supports rich blocks, backlinks, and optional deck or sheet modes.

Instructions

Create a page in a space (editor+). Body is markdown; tela://page/{id} links and [[Page Title]] wikilinks (resolved by title within the space) are indexed as backlinks. 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
bodyYesmarkdown body
propsNooptional page properties (frontmatter); free-form keys, reserved keys like id/title/slug/created are ignored
titleYespage title
space_idYesid of the space to create the page in
parent_idNooptional parent page id
idempotency_keyNooptional client-generated key; a retry with the same key returns the original result instead of creating a duplicate page (safe retries after a dropped connection)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
Behavior5/5

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

Annotations already indicate a write operation (readOnlyHint=false) with no destruction (destructiveHint=false). The description adds significant behavioral context: backlinks are indexed for tela:// links and wikilinks, tela renders a rich block palette beyond plain markdown, and special content types (decks, sheets) require different body format and properties. This goes well beyond what annotations provide.

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 well-structured and front-loaded with the core purpose, then details. It is somewhat lengthy due to rich block palette enumeration and special case instructions, but every sentence earns its place. Minor conciseness improvements could be made, but overall effective.

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 tool's complexity (6 parameters, special content types, backlink indexing) and existence of an output schema, the description is thorough. It explains the body format, links, rich blocks, deck/sheet conventions, and directs to additional guides. No gaps are apparent for the agent to misuse the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. The description adds substantial meaning: body is markdown with special link types, and for decks/sheets the body format and props must be set differently; props have reserved keys; idempotency_key enables safe retries. These details greatly enhance understanding beyond the schema 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 explicitly states 'Create a page in a space (editor+).' It clearly distinguishes from sibling tools like update_page, patch_page, delete_page, and from deck/sheet authoring guides. The verb 'create' with resource 'page' is specific and unambiguous.

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 provides explicit guidance: when to use this tool (to create a page), and when not (for presentations/decks or spreadsheets, directing to deck_authoring_guide and sheet_authoring_guide). It also instructs to prefer rich blocks and read the authoring guide for syntax. This is exemplary usage differentiation.

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