Obsidian Everywhere

by junnnnnw00

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Rollback Bulk Edit

rollback_bulk_edit

DestructiveIdempotent

Undo bulk edits in Obsidian by restoring all files from a rollback snapshot created by bulk_replace or rename_tag.

Instructions

Restore every file from a rollback snapshot created by bulk_replace or rename_tag.

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": {
      "rollbackId": "<rollbackId>"
    },
    "name": "rollback_bulk_edit"
  }
}

Input Schema

Name	Required	Description	Default
`rollbackId`	Yes	Rollback ID returned by bulk_replace.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 24, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, which the description does not contradict. The description adds minimal extra behavioral context (e.g., that it restores 'every file from a rollback snapshot'), but this is largely redundant given the annotations.

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?

The description is a single, concise sentence with no wasted words. It is front-loaded with the key verb 'restore'.

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 simple tool with one parameter and no output schema, the description is fully complete. It clearly explains the tool's purpose and the source of the required parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers the only parameter with 100% description. The description adds value by stating that rollbackId is returned by bulk_replace, providing context not in the schema.

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 clearly states the action ('restore every file') and the specific resource ('rollback snapshot created by bulk_replace or rename_tag'). It distinguishes this tool from its siblings by specifying the exact source tools that generate the snapshots.

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?

The description implies usage when you have a rollbackId from bulk_replace or rename_tag, providing clear context. However, it does not explicitly state when not to use it or list alternatives beyond the implied sibling tools.

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