KocoDesk
KocoDesk tools let your AI assistant manage one website in a KocoDesk CMS install: explore the page tree, edit pages and content blocks, write and translate blog posts, update navigation and site settings, list drive files, and generate images (within a daily limit).
Your administrator connects a site-bound API key from KocoDesk (Sites → AI). Writes only happen after you confirm.
Blog tools need the Blog plugin enabled for your site. Categories are read-only — create and rename them in the KocoDesk admin.
The tools
| Tool | Purpose |
|---|---|
| Context | Bootstrap: site, theme, components, page list, drive root |
| Get site | Full site details and settings |
| Page structure | Flat page tree for a language |
| List components | Available content block types |
| Get component | Field definition for one block type |
| Get page | One page by id |
| Get page content | Content blocks on a page |
| Create page | Add a page (after confirm) |
| Update page | Change page fields (after confirm) |
| Delete page | Remove a page (after confirm) |
| Create content | Add a content block (after confirm) |
| Update content | Edit a content block (after confirm) |
| Delete content | Remove a content block (after confirm) |
| Get navigation | Read a menu (e.g. main) |
| Update navigation | Change a menu (after confirm) |
| Update site settings | Meta, AI instructions, languages (after confirm) |
| List files | Files under the site drive folder |
| Generate image | AI image into the drive (after confirm; daily limit) |
Blog
| Tool | Purpose |
|---|---|
| Get blog settings | Blog URLs, RSS path, category root |
| Update blog settings | Change those settings (after confirm) |
| List blog posts | Browse and search posts |
| Get blog post | One post with categories and translations |
| Create blog post | Add a post (after confirm) |
| Update blog post | Edit a post or its translation (after confirm) |
| Delete blog post | Remove a post and its body (after confirm) |
| Translate blog post | Add a language version (after confirm) |
| Get blog post content | Content blocks in the article body |
| Create blog post content | Add a block to the article (after confirm) |
| List categories | Category tree for tagging posts |
How they work together
Context / structure → learn site + page ids
Components → learn valid block types before writing
Page / content get → inspect current content
Create / update / delete → change pages or blocks (after confirm)
Nav / settings → menus and SEO / AI guidance
Files / generate → media under drive root
Typical flow — add a landing section
- Context or structure to find the page.
- List components / get component for the block type.
- Ask to create content and explicitly confirm.
Typical flow — publish a blog post
- Get blog settings to confirm the blog is set up, then list categories for the ids you want.
- Create blog post with the title, teaser and categories.
- Create blog post content for each section of the article.
- Optionally translate it and edit the translated text with update blog post.
Tips
- Pass a language when working with translations (default is the primary language).
- Image generation is limited per day by your account setup; one image per request.
- Deleting a page fails if it still has child pages or is the site root.
- A blog post's title and teaser are separate from its article body: the body is made of content blocks.
- A post's publish date, lead image and categories are shared by all languages; only the text differs per translation.
Related
- User manual index
- Developer tools catalog