Skip to main content
Glama
Sign In

Replai

by tw.replai
OverviewDiscussionsAdmin

Restore publication to draft

publication_restore
DestructiveIdempotent

Restores historical configuration into a new draft, using revision and retained key.

This does not publish, restore deleted source bytes, undo messages or change channels.

Input Schema

NameRequiredDescriptionDefault
versionYesPublished configuration version from publication_history to restore into the draft.
agent_idYesAgent ID from agents_list or agent_create.
request_keyYesClient-generated request UUID; identical retries retain this key.
expected_revisionYesCurrent draft_revision from agent_draft_read; stale revisions fail.

Output Schema

NameRequiredDescriptionDefault
draftYes
effectYes
replayedYes
request_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / $defs / ConversationPolicy / description
      Previous value: -"Conversation-level rules, stored as JSONB on ``bot_configs.conversation_policy``.\n\nStored legacy keys, such as the retired Agent-wide ``mode``, are ignored on read.\nWho answers first is each channel's ``reply_mode``."New value: +"Conversation-level rules, stored as JSONB on ``bot_configs.conversation_policy``.\n\nWho answers first is each channel's ``reply_mode``."
  2. Changed4 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"Agent ID from agents_list or agent_create."
    • addedInput schema / properties / expected_revision / description
      Added value: +"Current draft_revision from agent_draft_read; stale revisions fail."
    • addedInput schema / properties / request_key / description
      Added value: +"Client-generated request UUID; identical retries retain this key."
    • addedInput schema / properties / version / description
      Added value: +"Published configuration version from publication_history to restore into the draft."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, destructive, idempotent, and closed-world behavior. The description adds valuable scope clarification: restoration goes into a new draft and does not affect live publication, messages, channels, or deleted source bytes, which meaningfully qualifies the destructive hint.

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?

Two tight sentences, front-loaded with the core action and followed by precise exclusions. Every sentence carries useful information.

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?

With full schema coverage, rich annotations, and an output schema, the description supplies the remaining non-obvious behavioral context: draft-only restoration and the specific things it does not do. Nothing essential for correct invocation 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 all four parameters are already documented in the schema. The description adds only a light reference to using revision and retained key, without introducing syntax or constraints beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: it restores historical configuration into a new draft. It distinguishes the action from publishing and other nearby operations, though it does not name the sibling tools publication_history or publication_publish explicitly.

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 clear context for use (restoring historical configuration into a draft) and useful exclusions (does not publish, restore deleted source bytes, undo messages, or change channels). It stops short of naming the alternative tool to use for those excluded actions.

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

All Replai toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources