What AI apps can do
Last updated: · Published:
An AI app works with Plate through tools. Which tools it gets depends on what you allowed when you connected it. Inside a site, your own role decides, the same way it does in the dashboard.
Tools
Reading (always available)
| Tool | What it does |
|---|---|
list_sites | Lists the sites the connection may use, with the partner and company of each site and whether prerendering is on. Can filter on a partner or company |
list_organizations | Lists the partners and companies of those sites, with how many of the sites each has |
describe_content_model | Shows a site's content types, their fields and the templates of section and element types. Per field: whether it is required, for a choice field its options and default, on which post templates the field is left out, and whether its value is hidden from AI apps. Can return a short summary, or only the types you ask for, and says where a section type is used |
search_content | Finds posts and content objects of one content type |
get_content | Reads one post, content object, section or element with all its field values, and for a post its template. Can find a post by its path or by its full address on one of the site's own domains, and can include the items of reference fields |
get_post_structure | Shows a post as a tree: sections, rows, columns and elements, with the short settings of each section |
search_media | Finds images and files in the media library, lists the folders, can list only images without alt text, and says how many files match |
get_site_settings | Shows the site settings in one language: the plain settings with their values, and every list the settings own, such as the menus, with its items, sub items and the post each item links to |
get_trays | Shows the trays of a site, such as the footer, built like a section of a post: fields, rows, columns and elements |
search_redirects | Lists the redirects of a site, or every redirect that leads to one post |
get_version_history | Lists the latest changes on a site: what changed (with the item's title), when, by whom and through which AI app |
Create and edit content
| Tool | What it does |
|---|---|
create_post | Creates a post. It can build the whole post with its sections in one call. New posts are drafts unless you ask to publish |
create_content_object | Creates a content object, such as a team member or a product |
update_content | Changes fields of a post, content object, section or element. A tray is a section, so this changes a tray's fields too |
duplicate_post | Copies a post with all its sections. With another language, the copy is linked as a translation |
add_section | Adds a section to a post, with its rows, columns and elements |
add_row, add_element | Add a row or an element to a section of a post, or to a tray |
copy_section | Copies a section with everything in it into a post |
set_column_widths | Changes the widths of the columns in a row of a post or a tray |
move_item | Reorders the sections of a post, or moves an element within a post or a tray |
upload_media | Adds an image or PDF to the media library |
update_media | Changes the alt text (per language) or the title of a file in the media library, or moves it to another folder |
create_media_folder | Adds a folder to the media library |
create_upload_link | Gives you a short-lived page to upload files yourself |
create_preview_link | Gives you a link that shows a post, also a draft, as it will look on the site. It works without logging in and expires after 7 days unless you ask for another period (at most 30) |
update_site_settings | Changes plain fields of the site settings, such as a copyright text or a color |
save_site_settings_item | Adds an item to a list of the site settings, such as a menu or a submenu, at the place you ask for, or changes an item: its fields, its place, or the item it sits under. A link to a post stays tied to that post |
save_redirect | Adds a redirect from an old address to a new one, or changes an existing one. Not needed after changing a post's slug: Plate adds that redirect itself |
Delete content
| Tool | What it does |
|---|---|
delete_content | Deletes a post or content object |
remove_item | Removes a section, row or element from a post, or a row or element from a tray |
delete_site_settings_item | Removes an item from a list of the site settings, such as a menu item, together with its sub items. The posts they linked to are not deleted |
delete_redirect | Removes a redirect |
delete_media | Deletes a file from the media library for good. A file that is still used in content is not deleted; the app is told where it is used |
Most AI apps ask you to confirm before they run these tools.
Switch prerendering
| Tool | What it does |
|---|---|
set_prerendering | Switches prerendering on or off for up to 10 sites per call |
This needs Create and edit content on the connection, and a role that may change the site's settings in Plate.
Site settings, menus and trays
The site settings and the trays belong to the site, not to a post. They follow the permission on the site settings: changing them needs a role that may edit the site settings, seeing them needs a role that may view them.
Site settings. An AI app sees two things: the plain settings (texts, colors, images) and the lists the settings own. A menu is such a list. So are button styles, footer links or the fields of a form, depending on the theme. The app can change a plain setting, and add, change, move or remove the items of any list.
Plate does not know which list is a menu, because every theme names its own. A list whose items have a link is marked as a likely menu. When a site has several, the app goes by the name and title of the list, and asks you when it is not clear.
Sub items are added and changed one at a time. A change to a menu item never replaces or removes its sub items.
Trays. A tray is a block the theme shows on every page, usually the footer. It is built like a section of a post, so the same tools work on it: the app can change its fields and add, move or remove rows and elements. Which trays a site has is part of the theme: an AI app cannot add, remove, move or rename a tray.
Fields hidden from AI apps
Themes keep API keys, tokens and passwords in content fields, in the site settings or in a post. An AI app does not get the value of a field that is hidden from AI apps. It sees that the field exists and whether it is filled in. It can still fill the field in when you give it the value.
You hide a field in the content model: open the field, go to the Advanced tab and switch on Hide the value of this field from AI apps. The switch is there for the fields of a site and for the field definitions of a theme.
When AI apps were introduced, Plate switched it on for the existing fields and field definitions whose name says they hold a secret, such as api_key, client_secret, access_token or password, or a name that ends in _key.
A field you add later is not hidden by itself, whatever its name: switch it on when the field holds a secret. The same goes for a key in an existing field with a neutral name, such as
codeorvalue. A key inside a longer text, such as a script in a<head>injection field, cannot be hidden: the switch hides whole fields.
A hidden field is also left out of the titles and summaries an AI app sees, and of its searches.
What you can rely on
- Version history. Every change an AI app makes is in the site's version history, marked with your name and the app, for example "Jane Doe via Claude". You can roll it back like any other change.
- Checked before saving. Unknown fields, choice values that are not one of the field's options, references to content of another site and invalid layouts are refused. A request with an invalid part saves nothing.
- References work. Reference fields are saved with all their values. An item inside a reference field, such as a button in a button group, can be read and changed by itself.
- Secrets stay in Plate. The value of a field that is hidden from AI apps is never sent to the app. See Fields hidden from AI apps.
- One site at a time. An item of one site cannot be read or changed through another site, and a full address only finds a post on that site's own domains.
- Synced content stays read-only. Content that is synced from another site can only be changed on that site.
- Drafts by default. A new post is a draft unless you ask the app to publish it.
- A link to check the result. A published post comes with its address, so the app (or you) can open the page after a change. For a draft the app can make a preview link. On a site with prerendering, the app is told whether the change marked the stored pages stale; if so, the next visit shows the new version.
Limits
| Limit | Value |
|---|---|
| Requests | 120 per minute per connection |
| Changes | 30 per minute per site |
| Deletes | 100 per hour per connection and site, unless your partner or company set another number |
| Images and files | JPEG, PNG, GIF, WebP, AVIF and PDF. Up to 20 MB from a URL or an upload page |
| Upload page | Works for 10 minutes, for at most 20 files |
| Layout | One desktop layout. Columns are full width on mobile |
When an AI app reaches a limit, Plate tells it to stop. You can continue in the dashboard, or with the app a little later.
SVG files are not accepted through AI apps, because an SVG can contain scripts. Add SVG files in the dashboard.
What stays in the dashboard
AI apps cannot:
- change the content model (content types and fields)
- edit theme files
- read form submissions
- change domains, users or roles
- add, remove or rename a tray
- delete a folder from the media library
- read the value of a field that is hidden from AI apps
- roll a site back to an earlier moment (they can read the version history, not restore it)
- set different layouts per breakpoint