Skip to main content
Glama
Sign In
obsidian-mcp-pro

obsidian-mcp-pro

by rps321321
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Edit Block

edit_block
DestructiveIdempotent

Replace the content of a block tagged with ^id in an Obsidian note while keeping the trailing anchor, so existing transclusions and references to that paragraph or list item continue to resolve.

Instructions

Replace the content of a block tagged with ^id. The trailing ^id anchor is preserved on the last line of the new content so existing transclusions (![[note#^id]]) keep working. Use to update a single paragraph or list item that other notes reference.

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": {
      "path": "<path>",
      "block": "<block>",
      "newContent": "<newContent>"
    },
    "name": "edit_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesVault-relative path to the note.
blockYesBlock id with or without the leading `^` (e.g. `myid` or `^myid`).
newContentYesReplacement content. The `^id` anchor is appended automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / newContent / maxLength
      Added value: +1000000
  2. Addedv2.0.0
  3. Removedv1.9.0
  4. Addedv1.8.0

TDQS

A4/5.0
Behavior4/5

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

Adds genuinely useful behavior beyond the annotations: the `^id` anchor is re-appended to the last line so existing `![[note#^id]]` transclusions keep working, which is the key side effect an agent must anticipate. Annotations already cover destructiveness and idempotency, so this extra context is what pushes it above baseline.

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?

Three short sentences, front-loaded with the core action, followed by the non-obvious anchor-preservation behavior and then the use case. No redundancy or filler.

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?

All three parameters are documented in the schema, annotations cover safety profile, and the description covers the most critical behavior (anchor/transclusion preservation). It omits error behavior (e.g. what happens if the block id is not found), which is a minor but real gap.

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% and the schema already documents the `^`-optional block id and the automatic anchor append for `newContent`. The description adds no syntax or edge-case detail (e.g. multi-line content behavior) beyond what the schema provides, so baseline 3 applies.

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 and resource ('Replace the content of a block tagged with `^id`') and scopes it to anchored blocks, which separates it from sibling tools like `update_section` or `replace_in_note`. It does not name those siblings explicitly, so the differentiation is inferred from the resource qualifier rather than stated.

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 final sentence gives a clear use case: 'update a single paragraph or list item that other notes reference', implying this is the right tool when transclusions must survive. No explicit when-not guidance or named alternatives are given, keeping it out of 5 territory.

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

Deploy Server

Other Tools