Foliyo

Restore previous content

restore_revision

Destructive

Restore retained content as a new revision of an owned page. Preserves its current URL, access policy, recipients and tracking. Requires the current expectedRevision to prevent overwriting newer changes. Sends no notification email.

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>",
      "revision": "<revision>",
      "expectedRevision": "<expectedRevision>"
    },
    "name": "restore_revision"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`revision`	Yes
`expectedRevision`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / expectedRevision / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / revision / maximum
```
Added value: +9007199254740991
```
AddedSep 27, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the annotations by enumerating what is preserved (URL, access policy, recipients, tracking) and what is suppressed ('Sends no notification email'). 'As a new revision' plus the expectedRevision guard also makes the non-idempotent, optimistic-concurrency behavior legible, which the idempotentHint=false and destructiveHint=true flags alone would not convey.

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?

Four tight sentences, front-loaded with the effect and followed by preservation, precondition and side effects. No filler or restated name/title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description covers effect, preservation, side effects and concurrency, which is enough to call it correctly. It omits what the call returns (e.g. the new revision number) and any permission requirements, leaving minor gaps.

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 0%, so the description must carry all three parameters. It explains expectedRevision's role (concurrency guard) and implies id is the page and revision is the content version to restore, but never defines those two explicitly.

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?

States a specific verb+resource and its effect: 'Restore retained content as a new revision of an owned page.' This makes it clearly distinct from read-oriented siblings like get_revision and list_revisions, though it never names those siblings 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?

'Requires the current expectedRevision to prevent overwriting newer changes' gives a concrete precondition for safe invocation, and 'owned page' bounds the applicable scope. It stops short of stating when not to use it or naming an alternative tool.

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

All Foliyo tools Inspect

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

Need Help?