Skip to main content
Glama

Get wiki page history

get_wiki_page_history
Read-only

A wiki page's HISTORY: everything that happened to it in one list, newest first — each text version (created, edited, renamed, restored, an agent's proposal accepted), comments, approvals, required reading, reviews and answers to their remarks, deprecation marks, the page opened to somebody off its project, its secrets and secret files (a secret put there, read, changed, removed), embeds, files attached, replaced and taken off, the page moved in the tree, its labels changed, a comment deleted, a reader taken off its reading list, the page shown in or taken off a public project's showcase. Each row says 'kind' (text, comments, approval, reading, review, deprecation, secrets, access, other), 'type' (what happened), 'at', 'actor', 'via' — the door: ui (a person's screen), voice, api, mcp, agent, system; null where it was not recorded — and the facts it has: 'version', 'subject' (whom or what it is about), 'detail', 'note'. You see only rows about what you may see: a secret file's rows only if you manage that file, a secret's readings only if you may change it, a secret's changes only if you may read it, who read the page only if you lead its project, the showcase only if you are on the project; never a secret's value. 'kinds' narrows it ('approval,review'); 'before' is the 'next' of the previous call to go further back. For a version's text and what changed, see get_wiki_page with its version.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesPage id (as returned by search_wiki).
kindsNoOnly these kinds, comma-separated: text, comments, approval, reading, review, deprecation, secrets, access, other. Omit for all.
limitNoHow many rows, 1–200 (default 50).
beforeNoThe 'next' the previous call answered, to read further back. Omit for the newest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses newest-first ordering, row fields including kind/type/actor/via/subject, and extensive permission-dependent visibility rules. It also states a critical data-protection behavior: secret values are never exposed, even when secret-related rows are visible.

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 important scope and ordering are front-loaded, but the description is a single very dense sentence with a long enumeration of event types and row fields. Much of that enumeration duplicates the kinds list already provided by the schema, making the definition harder to parse than necessary.

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 read-only history tool with no output schema, the description is complete: it explains return-row structure, ordering, visibility restrictions, filtering, pagination, and where to go for version text or diffs. The remaining omissions, such as limit range, are already covered by the input schema.

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 id, kinds, limit, and before. The description reinforces kinds narrowing and pagination via before, but adds little semantic detail beyond the schema's own parameter 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 states a specific verb and resource: retrieving a wiki page's complete history as one newest-first list. It explicitly distinguishes this from get_wiki_page for version text and diffs, so an agent can identify the tool's scope without opening the schema.

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?

It gives a clear alternative for version text and change details by directing the agent to get_wiki_page with its version. It also explains how to narrow by kinds and paginate with before, though it does not explicitly contrast with more specialized sibling tools such as approval, reading, or review history.

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