Skip to main content
Glama

update_frontmatter

Modify metadata properties in Obsidian notes while preserving the main content, enabling organized documentation management.

Instructions

Update frontmatter properties of a note without changing the body content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesRelative path to the note
propertiesYesJSON string of key-value pairs to set in frontmatter

Implementation Reference

  • The actual implementation of the update_frontmatter logic, which parses existing frontmatter, merges it with new updates using gray-matter, and stringifies it back.
    export function updateFrontmatter(
      content: string,
      updates: Record<string, unknown>,
    ): string {
      const parsed = matter(content);
      const merged = { ...parsed.data, ...updates };
      return matter.stringify(parsed.content, merged);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It indicates a mutation operation ('update') but lacks details on permissions, error handling (e.g., if the note doesn't exist), whether changes are reversible, or side effects. The description adds minimal behavioral context beyond the basic action.

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, efficient sentence with zero waste. It is front-loaded with the core purpose and includes a useful constraint ('without changing the body content'). Every word earns its place, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 (mutation with 2 parameters), no annotations, and no output schema, the description is minimally adequate. It covers the basic operation but lacks details on behavioral traits, error cases, or output expectations. It meets the minimum viable threshold but has clear gaps in completeness.

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 the schema fully documents both parameters ('path' and 'properties'). The description does not add meaning beyond the schema, such as explaining frontmatter format or path conventions. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 specific action ('update'), target resource ('frontmatter properties of a note'), and scope limitation ('without changing the body content'). It distinguishes this tool from siblings like 'append_to_note' or 'prepend_to_note' that modify body content, and from 'create_note' or 'delete_note' that handle different operations.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools like 'search_by_frontmatter' for querying or 'create_note' for initial setup, nor does it specify prerequisites such as requiring an existing note. Usage is implied but not explicitly stated.

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

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