Skip to main content
Glama
jagoff

obsidian-mcp-complete

by jagoff

obsidian_batch_create_notes

Create multiple Obsidian notes in a single API call, with each note's success or error reported independently. Supports optional vault, frontmatter, and overwrite settings.

Instructions

Create many notes in one call. Each item reports success or error independently unless stopOnError is true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vaultNoOptional configured vault name. Defaults to the server default vault.
notesYes
stopOnErrorNo

Implementation Reference

  • src/tools.ts:649-671 (registration)
    Registration and handler for obsidian_batch_create_notes. Defines the schema (vault, notes array with path/content/frontmatter/overwrite, stopOnError) and inline handler that iterates over notes, stringifies frontmatter if provided, writes each note via vaults.writeText, and collects per-note success/error results.
    tool(
      "obsidian_batch_create_notes",
      "Create many notes in one call. Each item reports success or error independently unless stopOnError is true.",
      {
        vault: vaultArg,
        notes: z.array(z.object({ path: z.string(), content: z.string().default(""), frontmatter: z.record(z.unknown()).optional(), overwrite: z.boolean().optional().default(false) })).min(1).max(100),
        stopOnError: z.boolean().optional().default(false),
      },
      async (args) => {
        const results = [];
        for (const note of args.notes) {
          try {
            const text = note.frontmatter ? stringifyFrontmatter(note.frontmatter, note.content) : note.content;
            results.push({ ok: true, ...(await vaults.writeText(vaults.notePath(note.path), text, args.vault, { overwrite: note.overwrite })) });
          } catch (error) {
            results.push({ ok: false, path: note.path, error: error instanceof Error ? error.message : String(error) });
            if (args.stopOnError) break;
          }
        }
        return { results };
      },
      { destructiveHint: false },
    );
  • Zod schema for obsidian_batch_create_notes: accepts an array of 1-100 notes, each with required path, optional content (default ''), optional frontmatter record, optional overwrite (default false), and a top-level stopOnError flag.
      vault: vaultArg,
      notes: z.array(z.object({ path: z.string(), content: z.string().default(""), frontmatter: z.record(z.unknown()).optional(), overwrite: z.boolean().optional().default(false) })).min(1).max(100),
      stopOnError: z.boolean().optional().default(false),
    },
  • src/index.ts:23-24 (registration)
    Entry point: registerObsidianTools is called in createObsidianMcpServer, which registers all tools including obsidian_batch_create_notes on the MCP server.
    registerObsidianResources(server, vaults, config);
    registerObsidianTools(server, vaults, config);
Behavior4/5

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

Annotations are minimal (all false), and the description adds value by disclosing the independent reporting feature and the stopOnError flag, which are behavioral traits beyond 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 two concise sentences with no wasted words, front-loading the core purpose.

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 no output schema and minimal annotations, the description is brief but covers key behaviors. However, it lacks information about return format, prerequisites, and the maxItems limit from the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 33% (only vault described). The description adds no additional meaning to the parameters notes and stopOnError, which are critical for correct 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 'Create many notes in one call', using a specific verb and resource, and distinguishes it from single-note creation tools like obsidian_create_note.

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 description explains error handling behavior ('Each item reports success or error independently unless stopOnError is true'), but does not explicitly state when to use batch vs single creation or mention alternatives.

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

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