Skip to main content
Glama
bezata

kObsidian MCP

Create Task

tasks.create

Append a new task line to an Obsidian note using the Tasks plugin format. Supports priority, due dates, recurrence, and other metadata. Returns the line number where the task was inserted.

Instructions

Append a new task line to a note. The task is written in Tasks-plugin format: - [ ] <content> {metadata emojis}. Optional metadata (priority, dueDate, scheduledDate, startDate, doneDate, createdDate, recurrence) is encoded as the plugin's convention emojis (🔺⏫📅⏳🛫✅➕🔁). Returns the standard mutation envelope with the 1-based lineNumber where the task was inserted.

Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.

Examples:

Example 1 — Append a simple task with a due date:

{
  "filePath": "Tasks.md",
  "content": "Write the v0.3.0 migration doc",
  "dueDate": "2026-05-01"
}

Example 2 — Append a high-priority weekly recurring task:

{
  "filePath": "Tasks.md",
  "content": "Weekly review",
  "priority": "high",
  "recurrence": "every week on Sunday"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesNote to append the task to.
contentYesTask body text (without the `- [ ]` checkbox).
statusNoInitial checkbox state. Default `incomplete`.
priorityNoTasks-plugin priority level.
dueDateNo
scheduledDateNo
startDateNo
doneDateNo
createdDateNo
recurrenceNoTasks-plugin recurrence expression, e.g. `every day`, `every week on Monday`, `every 2 weeks`.
vaultPathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
changedYesTrue if the tool altered vault state on this call; false if it was a no-op.
targetYesThe path or identifier the tool acted on.
summaryYesShort human-readable summary of what happened.
Behavior4/5

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

Annotations are present (readOnlyHint false, destructiveHint false) and the description adds valuable behavioral context: it appends tasks in Tasks-plugin format with emoji-encoded metadata, returns the lineNumber, and respects vault selection via vaultPath. No contradictions. Good disclosure of effects.

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?

The description is front-loaded with the core action, followed by format details, vault behavior, and examples. It is well-structured and not excessively long given the number of parameters. Minor redundancy could be trimmed, but overall efficient.

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?

Given the tool's complexity (11 parameters, 2 required) and the presence of an output schema, the description covers all essential aspects: task format, optional metadata encoding, vault selection, output (lineNumber), and examples. No gaps remain for an agent to misinterpret.

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 description coverage is only 45%, but the description compensates by explaining the task line format, emoji conventions, and giving two comprehensive examples. It clarifies how each optional metadata parameter maps to plugin emojis, adding meaning beyond the schema's basic 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's specific action: 'Append a new task line to a note.' It distinguishes from siblings like tasks.search, tasks.toggle, etc., by focusing on creation. The verb 'append' and resource 'task line' are precise.

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 explains how to use the tool (vault path selection, required parameters) but does not explicitly guide when to use it over alternatives like tasks.updateMetadata or tasks.toggle. It lacks comparison to sibling task operations, which would help an agent choose correctly.

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/bezata/kObsidian'

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