Obsidian Everywhere

Overview Schema Source Related Servers Discussions Admin

Bulk Replace

bulk_replace

Destructive

Replace text across notes in a selected folder, with optional regex matching. Previews changes by default and creates a rollback snapshot before applying.

Instructions

Replace text across notes selected by folder, optionally using regex. Defaults to dry-run, reports every changed file, enforces maxFiles, and creates a rollback snapshot before applying.

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": {
      "find": "<find>",
      "replace": "<replace>"
    },
    "name": "bulk_replace"
  }
}

Input Schema

Name	Required	Description
`find`	Yes	Literal text or JavaScript regex pattern.
`regex`	No	Treat find as a regular expression (default false).
`dryRun`	No	Preview only (default true). Set false to apply.
`folder`	No	Optional vault-relative folder scope.
`replace`	Yes	Replacement text; regex capture references such as $1 are supported.
`maxFiles`	No	Abort above this changed-file count (default 100).
`caseSensitive`	No	Regex case sensitivity (default true).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 24, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description goes beyond the annotations (destructiveHint=true) by detailing that it defaults to dry-run, reports changed files, enforces maxFiles, and creates a rollback snapshot. No contradictions with 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?

Two sentences, front-loaded with the core action, and no wasted words. Every sentence provides valuable behavior details.

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?

The description covers the key behavioral aspects of the tool (dry-run, rollback, maxFiles) and output reporting. Without an output schema, it could mention the return format, but the description is sufficient for understanding the tool's purpose and side effects.

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 each parameter is documented. The description does not add additional meaning beyond the schema, but it sets the overall context for parameter usage. Baseline of 3 is appropriate.

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 tool replaces text across notes selected by folder, with optional regex, and lists key default behaviors. This distinguishes it from sibling tools like replace_text, which likely operates on a single note.

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 explains the default dry-run behavior and safeguards (maxFiles, rollback), which helps the agent decide when to use it. However, it does not explicitly compare to alternatives like replace_text.

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