Skip to main content
Glama
adrienthebo
by adrienthebo

edit_note_section_tool

Edit specific sections in Obsidian notes by markdown heading to add, update, or replace content without rewriting entire files.

Instructions

Edit a specific section of a note identified by a markdown heading.

When to use:

  • Adding content to a specific section without rewriting the whole note

  • Updating a particular section (like status updates, task lists)

  • Inserting content at precise locations in structured notes

  • Building up notes incrementally by section

When NOT to use:

  • Simple append to end of note (use update_note with merge_strategy='append')

  • Replacing entire note content (use update_note)

  • Creating a new note (use create_note)

Section identification:

  • Sections are identified by markdown headings (# ## ### etc.)

  • Match is case-insensitive

  • First matching heading is used if duplicates exist

  • Section includes content until next heading of same/higher level

Operations:

  • insert_after: Add content immediately after the section heading

  • insert_before: Add content immediately before the section heading

  • replace: Replace entire section including the heading

  • append_to_section: Add content at the end of the section

Returns: Edit status including whether section was found or created

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the note to edit
section_identifierYesMarkdown heading that identifies the section (e.g., '## Tasks', '### Status')
contentYesContent to insert, replace, or append to the section
operationNoHow to edit the section. 'insert_after' = add content after heading, 'insert_before' = add before heading, 'replace' = replace entire section, 'append_to_section' = add to end of sectioninsert_after
create_if_missingNoCreate the section at the end of the note if it doesn't exist
ctxNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: section identification rules (case-insensitive, first match, content boundaries), operations (insert_after, insert_before, replace, append_to_section), and the create_if_missing option. However, it lacks details on error handling, permissions, or rate limits, which are relevant for a mutation tool. The description does not contradict any annotations, as none are present.

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 well-structured with clear sections (purpose, usage guidelines, section identification, operations, returns), each sentence adds value, and it avoids redundancy. It is appropriately sized for a tool with 6 parameters and complex behavior, front-loading the core purpose and usage guidelines for quick comprehension.

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?

Given the tool's complexity (6 parameters, mutation operation, no annotations, no output schema), the description is largely complete: it covers purpose, usage, behavioral rules, and parameter semantics. However, it lacks output details (only mentions 'Edit status' vaguely) and doesn't address potential errors or side effects, which are important for a tool that modifies notes. This minor gap prevents a perfect score.

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 description coverage is high (83%), so the baseline is 3. The description adds meaningful context beyond the schema: it explains how 'section_identifier' works with markdown headings and matching rules, clarifies the 'operation' options with practical examples, and mentions the 'create_if_missing' behavior. This compensates for the 17% coverage gap and provides valuable semantic understanding, though it doesn't detail all parameters (e.g., 'ctx' is unexplained).

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 starts with a clear, specific statement: 'Edit a specific section of a note identified by a markdown heading.' This explicitly states the verb ('edit'), resource ('specific section of a note'), and mechanism ('identified by a markdown heading'), distinguishing it from sibling tools like update_note_tool or create_note_tool. The purpose is unambiguous and well-articulated.

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 includes explicit 'When to use' and 'When NOT to use' sections, listing four use cases and three exclusions with named alternatives (e.g., 'use update_note with merge_strategy='append''). This provides clear, actionable guidance on when to select this tool over its siblings, such as update_note_tool for whole-note edits or create_note_tool for new notes.

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/adrienthebo/obsidian-mcp'

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