Create Task
tasks.createAdd a task to an Obsidian note with due dates, priority, recurrence, and other metadata, and get the inserted line number for reference.
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
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | Initial checkbox state. Default `incomplete`. | |
| content | Yes | Task body text (without the `- [ ]` checkbox). | |
| dueDate | No | ||
| doneDate | No | ||
| filePath | Yes | Note to append the task to. | |
| priority | No | Tasks-plugin priority level. | |
| startDate | No | ||
| vaultPath | No | ||
| recurrence | No | Tasks-plugin recurrence expression, e.g. `every day`, `every week on Monday`, `every 2 weeks`. | |
| createdDate | No | ||
| scheduledDate | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | The path or identifier the tool acted on. | |
| changed | Yes | True if the tool altered vault state on this call; false if it was a no-op. | |
| summary | Yes | Short human-readable summary of what happened. |