Skip to main content
Glama
bezata

kObsidian MCP

Update Fenced Block

blocks.update
DestructiveIdempotent

Update a fenced block's content in an Obsidian note while preserving its fences and language tag. Locate the block by blockId or index; the language guard prevents mismatched updates. The replacement source becomes the new block body.

Instructions

Replace one fenced block's body source-preservingly — the surrounding fences, language tag, and neighbouring content are untouched. Locate the block by blockId or index. language acts as a guard: if the located block is not of the declared language, the update fails. source is the replacement body WITHOUT the surrounding ``` fences. Idempotent — re-running with identical inputs is a no-op on the file contents. Destructive — overwrites the previous block body in place.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Examples:

Example 1 — Replace the first Mermaid diagram in a note:

{
  "filePath": "Diagrams/system-overview.md",
  "language": "mermaid",
  "index": 0,
  "source": "flowchart TD\n  A --> B"
}

Example 2 — Update a DQL query block by stable id:

{
  "filePath": "Dashboards/Inbox.md",
  "language": "dataview",
  "blockId": "inbox-open",
  "source": "TASK\nFROM #inbox\nWHERE !completed"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesPath of the note containing the block.
languageYesLanguage of the block being updated. Acts as a guard: update fails if the targeted block's real language does not match.
sourceYesReplacement source for the block body, WITHOUT the surrounding ``` fences. Surrounding newlines and indentation are preserved by the tool.
blockIdNoStable block identifier (e.g. `^abc123`). Takes precedence over `index` when both are given.
indexNo0-based position of the block within its language group in the file. Use when no blockId is available. Defaults to 0 (the first block).
vaultPathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
changedYesTrue if the tool altered vault state on this call; false if it was a no-op.
targetYesThe path or identifier the tool acted on.
summaryYesShort human-readable summary of what happened.
Behavior5/5

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

The description discloses key behaviors beyond the annotations: source-preserving nature (fences and neighboring content untouched), language guard, idempotency, destructiveness, vault selection logic, and that source should be without fences. No contradiction 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?

The description is concise and well-structured: a single summary sentence, followed by details in clear statements, then two precise examples. Every sentence adds value without redundancy.

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?

Given the tool's moderate complexity (6 params, 3 required, output schema exists), the description covers all necessary aspects: purpose, usage, parameter details, behavioral traits, and examples. No gaps remain.

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?

With 83% schema description coverage, the baseline is 3. The description adds significant value: explains language guard, source format, index default, blockId precedence, and vaultPath override. The one parameter without schema description (vaultPath) is addressed in the description. Examples further clarify usage.

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 primary action: 'Replace one fenced block's body source-preservingly' with a specific verb ('replace') and resource ('block body'). It distinguishes from sibling tools like blocks.list and blocks.read by emphasizing its destructive and idempotent nature, and details how to locate the block by blockId or index.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use the tool, including how to locate blocks (by blockId or index), the language guard, idempotency, and vault selection. Examples illustrate two common use cases. It implicitly contrasts with read/list tools by describing its destructive write operation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bezata/kObsidian'

If you have feedback or need assistance with the MCP directory API, please join our Discord server