obsidian-mcp

Create note

create_note

Create a new Markdown note in an Obsidian vault, auto-creating parent folders and optional YAML frontmatter, with overwrite support to replace existing notes.

Instructions

Create a new note. Fails if it already exists unless overwrite=true. Parent folders are created automatically. Pass frontmatter to have YAML properties generated; content is the markdown body.

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>",
      "content": "<content>"
    },
    "name": "create_note"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Vault-relative note path (.md optional)
`content`	Yes	Markdown body of the note
`overwrite`	No	Replace an existing note
`frontmatter`	No	Optional YAML properties, e.g. {"tags": ["research"]}

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Sep 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses duplicate-handling (fails unless overwrite), automatic parent-folder creation, and frontmatter generation. It could add more about return values or the destructive nature of overwrite, but key side effects are transparent.

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, front-loaded sentences. The core action comes first, followed by edge-case behavior and parameter semantics. Every sentence adds useful information with no 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?

The description covers the essential facts for a create operation: existence check, overwrite behavior, parent-folder creation, and parameter roles. With no output schema and no annotations, a brief note on return value or error behavior would be a small enhancement, but the current coverage is strong.

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?

Schema coverage is 100%, so the baseline is 3. The description adds extra meaning beyond the schema by explaining that parent folders are created automatically for path, that frontmatter gets turned into generated YAML, and that content is the markdown body. These details help the agent pass the correct values.

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 a specific verb and resource: 'Create a new note.' It also discloses an overriding behavior (fails if exists unless overwrite=true) that distinguishes it from edit_note and other siblings, so there is no ambiguity about what the tool does.

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

Usage Guidelines3/5

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

The description implies usage: it is for creating new notes, and the overwrite/fails behavior gives some context. However, it does not explicitly say when to prefer this over edit_note or when not to use it, leaving the routing decision to inference.

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

Deploy Server