Skip to main content
Glama
aleksakarac

Obsidian MCP Extended

by aleksakarac

update_task_metadata_tool

Update priority, dates, or recurrence of Obsidian tasks without altering the task description. Pass null to remove metadata fields.

Instructions

Update task metadata without changing the task content (filesystem-native).

Updates priority, dates, or recurrence patterns while preserving the task description. Pass null/None to remove metadata fields.

When to use:

  • Rescheduling tasks

  • Changing task priorities

  • Adding/removing recurrence

  • Batch metadata updates

Returns: Success status, updated line, and list of changes made

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to file containing the task (relative to vault)
line_numberYesLine number containing the task
priorityNoUpdate priority (null to remove)
due_dateNoUpdate due date YYYY-MM-DD (null to remove)
scheduled_dateNoUpdate scheduled date YYYY-MM-DD (null to remove)
start_dateNoUpdate start date YYYY-MM-DD (null to remove)
recurrenceNoUpdate recurrence pattern (must start with 'every', null to remove)
vault_pathNoPath to vault (optional, uses OBSIDIAN_VAULT_PATH env if not provided)
ctxNo
Behavior3/5

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

No annotations provided. Description states metadata is updated while preserving content, and null removes fields. Lacks details on permissions, idempotency, or side effects for unchanged fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with key purpose, then usage and returns. Structure is clear but could slightly reduce verbosity (e.g., remove redundant 'filesystem-native' explanation).

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?

Covers purpose, parameters usage, and return value. Lacks error handling or behavior when task not found. Given 9 params and no output schema, it is mostly complete.

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 coverage is high (89%). Description adds the concept of passing null to remove fields, but otherwise does not add meaning beyond schema descriptions.

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 tool updates task metadata (priority, dates, recurrence) without changing content, and differentiates from siblings like create_task_tool by specifying it modifies existing tasks. The phrase 'filesystem-native' indicates direct file modification.

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?

Includes a 'When to use' section listing rescheduling, changing priorities, and adding/removing recurrence. Does not explicitly state when not to use or mention alternatives like update_note_tool for content changes.

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

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