Skip to main content
Glama

Bring back an older version as a NEW version (history is never rewritten). Also undeletes a deleted doc.

restore_doc_version

Bring back an older version as a NEW version (history is never rewritten). Also undeletes a deleted doc.

Undo a bad edit: brings back the version at at (a commit from get_doc_history) as a NEW version — history is never rewritten. version = the doc's current version from get_doc, or null when the doc is deleted (this also undeletes it). Brief, notes and handoffs only.

WRITE: version must be the version from your latest read of this file (get_issue for issues, list_comments for comments, list_sprints for sprints, get_doc for project docs, read_file for md files). If the file changed since, the call fails with 409 version_conflict and the error contains the current file (details.current, details.current_version): re-read it, re-apply your change on top of the current content and retry with the new version. Never overwrite someone else's change blindly — if your change and theirs disagree, ask the user which to keep.

You act with exactly the rights of the user who owns this token; a project you cannot see returns not_found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atYesThe `commit` of the version to bring back (get_doc_history).
kindYes
slugYesFile name of a doc without `.md`: lowercase a–z 0–9 and `-` (brief, notes, company brief) or `H-{n}` (handoffs).
messageNo
versionYesCurrent version of the doc; null when it is deleted.
project_keyYesProject key, e.g. `KJ`. 2–10 chars, uppercase letters and digits, starts with a letter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources