Capacities

Insert markdown as new block(s) on an object. - When afterBlockId is set, insert immediately after that sibling (UUID from readObjectBlocks). - When afterBlockId is omitted or empty, insert at the beginning of the object's default blocks property. Discover block IDs with readObjectBlocks before using afterBlockId.

addBlock

Append markdown content to an existing object. Inline date chips (pink date references) can be created with: - `[[Date/<natural language or ISO date>]]` (preferred), e.g. `[[Date/2026-07-14]]` or `[[Date/14 Jul 2026]]` - `[[<parseable date>]]` bare wikilink, e.g. `[[2026-07-14]]` - `+date/<parseable date>/` path syntax, e.g. `+date/2026-07-14/` Plain text dates without wikilink syntax remain plain text. Timezone: The user's timezone is Europe/Madrid. Interpret "today"/"tomorrow"/calendar dates in this timezone, not UTC: for day dates provide the calendar day in Europe/Madrid (YYYY-MM-DD), and for precise times provide the instant with the correct UTC offset for Europe/Madrid (e.g. 15:30 in Europe/Madrid as "15:30:00-04:00" or its UTC equivalent) so wall-clock times match the user's local timezone.

appendMDToObject

Create a clickable link for an object ID. Use in your response when: Citing or referencing specific objects in your answer; You want the user to easily navigate to mentioned objects.

createObjectLink

Create a new object by object type (title or plural, e.g. "Page", "Books") using markdown. Each createObjectViaMD call creates exactly ONE object. There is no bulk mode: you cannot create several objects in a single call. To create multiple objects, call this tool once per object. **Required:** Call getObjectTypeShape with the same objectType first. Include every writable property you intend to set using the exact frontmatterKey values returned. Markdown import uses the same pipeline as Public API POST /object/markdown. **Required:** Call getObjectTypeShape with the same objectType first. Use only the frontmatterKey values it returns for properties on that object type. Document shape: 1. Optional YAML frontmatter between --- lines (writable object properties). 2. Markdown body after the closing --- (block content — not frontmatter). The createObjectViaMD title argument is always merged into frontmatter as title: (overrides an existing title key). Aliases: set the aliases frontmatter key ONLY when the object has a genuinely different name that is NOT already contained in the title and would help search find it (e.g. title "Darth Sidious" -> alias "Emperor Palpatine"). Do NOT add short forms, nicknames, abbreviations, or partial names already in the title (e.g. title "Peter Pan" -> alias "Peter"). Most objects need no aliases — omit the key unless a clearly distinct alternative name exists. Body-only markdown (no --- block): the tool wraps your input as: --- title: "Your title" --- # Optional heading Body paragraphs... If your markdown already starts with ---, only the title argument is injected/updated in that block; the rest is imported as-is. Avoid duplicating the title as a lone # heading unless you want it removed during import when it matches the title property. Timezone: The user's timezone is Europe/Madrid. Interpret "today"/"tomorrow"/calendar dates in this timezone, not UTC: for day dates provide the calendar day in Europe/Madrid (YYYY-MM-DD), and for precise times provide the instant with the correct UTC offset for Europe/Madrid (e.g. 15:30 in Europe/Madrid as "15:30:00-04:00" or its UTC equivalent) so wall-clock times match the user's local timezone.

createObjectViaMD

Create a new page (Page object) with a title and markdown body.

createPage

Create a new task (Task object) with a title, optional task properties (status, priority, date, deadline), and markdown notes body. `taskProps.date` can be a single date or a range (start + end). `taskProps.deadline` is a separate due date (same shape). - `dateResolution: "day"` for all-day tasks: `start` is the calendar day — pass "YYYY-MM-DD" (e.g. "2026-08-07") or "YYYY-MM-DDT00:00:00.000Z". A range uses two calendar days: { start: "2026-08-07", end: "2026-08-09", dateResolution: "day" }. - `dateResolution: "time"` for precise times: `start` (and optional `end`) are full ISO 8601 datetimes, e.g. { start: "2026-08-07T15:30:00.000Z", end: "2026-08-07T17:00:00.000Z", dateResolution: "time" }. Example: { date: { start: "2026-08-07", dateResolution: "day" } } For frontmatter keys and label options, call getObjectTypeShape with objectType "Task" first. Timezone: The user's timezone is Europe/Madrid. Interpret "today"/"tomorrow"/calendar dates in this timezone, not UTC: for day dates provide the calendar day in Europe/Madrid (YYYY-MM-DD), and for precise times provide the instant with the correct UTC offset for Europe/Madrid (e.g. 15:30 in Europe/Madrid as "15:30:00-04:00" or its UTC equivalent) so wall-clock times match the user's local timezone.

createTask

Remove one block by blockId (from readObjectBlocks). Nested child blocks are removed with it. Discover block IDs with readObjectBlocks first.

deleteBlock

Move an object to trash. User has 30 days to restore it before it is permanently deleted.

deleteObject

Retrieve object content as structured JSON: markdown content + typed properties, title, timestamps, object type, tags, and collections. Use when: - The snippet from search is not enough to answer the user prompt. - You need structured property values (including object links) to answer relationship queries (e.g. "Where does person X work?"). - You need the object title, type, timestamps, tags, or collection membership. Response fields: - id, spaceId, title, objectType, objectTypeId, createdAt, lastUpdated - properties: typed property map (title, text, number, boolean, url, date, label, entity, icon, aliases, richText). Entity-type values contain linked object IDs. - tags: array of tag names - collections: array of collection UUIDs - content: full markdown representation including YAML frontmatter; entity-relation properties are written as `[[Title]]` wiki links that can be sent back as-is (e.g. in updateObjectViaMD) without loss. Input: object ID (e.g., { id: "NOTE/abc123" }).

getObjectContent

Returns authoritative YAML frontmatter keys and value formats for an object type in this space. Call this before createObjectViaMD when you need to set properties accurately.

getObjectTypeShape