tela

Overview Schema Source Related Servers Discussions Admin

List pages

list_pages

Read-only

Browse a space's page hierarchy or find page IDs; filter by parent page, top-level, or draft/published status for navigation and lookup.

Instructions

Flat page listing in a space (read-only). Pass parent_id for the direct children of one page; omit for top-level pages. Use to browse a space's structure or find a page_id; to find pages by keyword use search, and to read a page's body use get_page.

Input Schema

Name	Required	Description
`status`	No	optional: 'draft' or 'published' to list only pages in that state; omit for all
`space_id`	Yes	id of the space to list pages in
`parent_id`	No	optional parent page id; omit for top-level pages

Output Schema

Name	Required	Description	Default
`pages`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.11.0Oct 15, 2026

addedInput schema / properties / status

Added value: +{
+  "description": "optional: 'draft' or 'published' to list only pages in that state; omit for all",
+  "type": "string"
+}

addedOutput schema / properties / pages / items / properties / status
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / pages / items / required

Previous value: -[
-  "id",
-  "space_id",
-  "parent_id",
-  "title",
-  "position",
-  "url"
-]New value: +[
+  "id",
+  "space_id",
+  "parent_id",
+  "title",
+  "position",
+  "status",
+  "url"
+]

First observedv0.1.0Jul 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful context beyond that: the listing is 'flat' (no recursive expansion) and the parent_id-omit behavior changes which level is returned. It stops short of describing pagination or result limits, but it is well ahead of a bare read-only flag.

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?

Three tight sentences: purpose and read-only first, then the parent_id scoping rule, then routing to alternatives. Every clause carries information and the load-bearing constraint is 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?

An output schema exists, so return shape need not be described, and the safety profile is fully carried by annotations. The description covers scope, the key parameter's effect, and sibling routing — nothing an agent needs to call this correctly is missing.

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 the schema already documents space_id, status, and parent_id. The description restates the parent_id omit-for-top-level rule rather than adding syntax, defaults, or formats beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 ('listing') and resource ('pages') plus the scope ('in a space', 'flat'). It distinguishes itself from search and get_page by name, so an agent can route correctly without opening a schema.

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 explicit use cases (browse a space's structure, find a page_id) and names the two alternatives with the conditions that select them: `search` for keyword lookup and get_page for reading a body. No inference required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.