Skip to main content
Glama

Get wiki page

get_wiki_page
Read-only

Get one wiki page by id, or by space key + title, if it is visible to this token. Returns the page text, its labels, its parent and child pages, its comments, and the issues linked to it. Pass withMarkdown: true when you intend to edit it — you then get the page's Markdown source to change and hand back to update_wiki_page, and each comment's own Markdown, version and anchor for update_wiki_comment. A large page is read a part at a time: 'outline' lists its headings and how big each section is, then 'section' returns one of them (or 'offset'/'limit' a run of lines), and update_wiki_page's 'edits' changes just the words you mean without sending the page back. A page with manim code blocks (where the company has scenes switched on) also returns 'scenes': each block's drawing state — queued, rendering, done or failed — manim's own error when it failed, and the attachment it was drawn into. A page with anim blocks (a scene as JSON the reader's client plays itself, no rendering) returns 'anims': for each, whether it can be shown, its length, or every problem with where it stands. A page marked no longer current returns 'deprecated' — since when, by whom, the reason, the page that replaces it and a note: read the replacement, and never quote a deprecated page as current or in force. A page with ```external-table blocks returns 'externalTables': each block's source, its columns and rows as data (the source's, cached, with 'fetchedAt'), or why it shows none — read a register from here rather than from its source.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_wiki_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoPage id (as returned by search_wiki).
limitNoHow many lines to return from 'offset' (default 200).
titleNoExact page title, when looking the page up by title.
offsetNoReturn only the Markdown source from this 1-based line on — for a page without headings to navigate by. Pair with 'limit'.
outlineNoReturn the page's table of contents instead of its body: per heading its level, text, anchor, the 1-based lines its section spans in the Markdown source, and its size in characters. Start here on a large page.
sectionNoReturn only this section's Markdown — its heading line down to the next heading of the same or a higher level, subsections included. Name it by its anchor (as 'outline' gives it: the id a {toc} entry links to) or by its heading text.
spaceKeyNoSpace key, when looking the page up by title.
withRelatedNoWith 'outline', 'section' or 'offset': also return the page's children, attachments, comments and linked issues, which a partial read otherwise leaves out.
withMarkdownNoReturn the Markdown source ('markdown') instead of the plain text — what to edit and pass back to update_wiki_page, and, for each comment, to update_wiki_comment. Off by default: reading costs less as text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/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 meaningful behavior beyond that — token-visibility filtering, partial reads via outline/section/offset, cached external-table rows with 'fetchedAt', and per-block scene states — but it is written as a catalog of return shapes rather than disclosure of operational constraints (cost of a full read, size thresholds, what 'visible to this token' excludes). Solid added value, not exhaustive.

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 lookup and edit-intent guidance is front-loaded, which is good. However the remainder is a single dense block of conditional clauses about manim blocks, anim blocks, deprecated pages and external tables, several of which apply to rare page types and bury the common path. It is information-rich but under-structured, with no separation between the frequent and the edge cases.

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?

For a 9-parameter, zero-required, no-output-schema tool, the description covers operand selection, partial-read strategy, the edit round-trip, and the special return shapes (scenes, anims, deprecated, externalTables) that an agent could not otherwise anticipate. Nothing needed to call it correctly or interpret the response 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% and the schema already explains outline, section, offset/limit, withRelated and withMarkdown in detail, so the baseline is 3. The description does add intent framing the schema lacks — withMarkdown is for editing workflows, withRelated compensates for partial reads, offset/limit is the fallback for pages without headings — but the mechanics themselves are repeated rather than extended.

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 ("Get one wiki page") and immediately enumerates the two lookup modes (by id, or spaceKey + title) plus the token-scoped visibility condition. It goes on to list exactly what comes back — text, labels, parents/children, comments, linked issues — which lets an agent separate it from search_wiki and the get_wiki_page_* siblings.

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?

Explicit conditional routing: 'Pass withMarkdown: true when you intend to edit it', 'read a register from here rather than from its source', 'Start here on a large page' for outline, and the recommendation to use update_wiki_page's 'edits' instead of round-tripping the whole page. It also names the exact sibling to hand results back to (update_wiki_page, update_wiki_comment), including a when-not rule for quoting deprecated pages.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources