Skip to main content
Glama
stonematt

mcp-obsidian-cli

by stonematt

obsidian_property_set

Set or update a frontmatter property in an Obsidian note by specifying property name, value, and optional type (text, list, number, checkbox, date, datetime). Target notes by file name or exact path.

Instructions

Set a frontmatter property on a note.

Parameters: name (required) — property name value (required) — property value (see type for multi-valued props) type (optional) — property type: text (default) | list | number | checkbox | date | datetime file (optional) — note name (wikilink resolution) path (optional) — exact file path One of file or path is required.

Multi-valued properties (tags, aliases, Links, etc.): You MUST pass type="list" AND a JSON-array string as value. Without type="list" the value is written as a single scalar string — a comma-separated value is NOT split into YAML list items, and bracketed wikilinks are never split. Use a JSON array universally; it is unambiguous for both plain strings and wikilinks.

Examples: obsidian_property_set({ name: "status", value: "done", file: "My Task" }) obsidian_property_set({ name: "tags", value: "["project", "active"]", type: "list", path: "Work/todo.md" }) obsidian_property_set({ name: "Links", value: "["[[plan]]", "[[baseline]]"]", type: "list", file: "My Task" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoFile name
nameYesProperty name
pathNoFile path
typeNoProperty type. Use "list" for multi-valued props (tags/aliases/Links) with a JSON-array value; omitting it writes a scalar string
valueYesProperty value. For type="list", pass a JSON-array string, e.g. '["a", "b"]'
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. It explains critical behavior: without type="list", multi-valued values are written as scalar strings, comma-separated values are not split, and bracketed wikilinks are never split. It also clarifies the JSON-array requirement, but does not mention overwrite semantics or auth requirements, so it is not fully comprehensive.

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: a one-sentence purpose, a clean parameter list, a focused note on multi-valued behavior, and examples. Every section earns its place and the front-loaded opening gives immediate clarity.

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?

Despite having no output schema, the description covers all parameter semantics, addresses edge cases (wikilinks, list splitting), and provides examples. It is fully sufficient for an agent to invoke the tool correctly in most scenarios.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant meaning: it clarifies the relationship between type and value, specifies that one of file/path is required (an extra constraint beyond schema), and provides three concrete examples showing correct usage for both scalar and list properties.

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 opens with 'Set a frontmatter property on a note', using a specific verb and resource. It clearly distinguishes itself from sibling tools like obsidian_properties or obsidian_read by focusing on writing/updating a property.

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 provides clear context for when to use the tool (setting a property) and detailed guidance on file/path resolution and multi-valued properties. However, it does not explicitly mention alternatives or when not to use it, so it lacks explicit exclusions.

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

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