xtiles_create_tiles_from_markdown_in_project_planner
Destructive
Append tiles generated from Markdown into a project planner for the period containing the given date. Returns the affected view_id, tiles (each created tile's id and resource_url — a deep link that opens the page focused on that tile), and parent_resource_url (a link that opens the page the tiles were created on). New tiles arrive at one default size, in import order — arrange them next (xtiles_get_page_layout, then xtiles_set_page_layout for the ids returned here); how, and whether the page already passes, is in xtiles://guide/markdown/design.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | Anchor date (ISO 8601, e.g. "2026-04-24"). Tiles are created in the planner range containing this date. | |
| period | Yes | Planner period: e.g. "day", "week", "month". | |
| markdown | Yes | Markdown content to convert into tiles. Each top-level heading (`### Title`) typically becomes a separate tile; paragraphs, lists, and code blocks under a heading become its body. Tiles are appended to existing content (not replaced). Full syntax: read resource `xtiles://guide/markdown/overview` or call `xtiles_get_docs`. The target already exists, so continue its palette: read its tile colours (`xtiles_get_tile_styles`) before writing, and write the same colours inline (`@color` / `@colorSize`). Rules: `xtiles://guide/markdown/design`. | |
| projectId | Yes | Project ID whose planner is the target. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tiles | No | ||
| view_id | No | ||
| tile_ids | No | ||
| parent_resource_url | No |