What each area can do

Tool names are <area>_<tool>, for example site_insert_block or cms_create_entry. Your assistant lists the exact tools available to you.

site

Find and create pages (static pages, CMS templates, product and collection templates, search and 404 pages), insert sections from the library or whole block trees, edit text, media, props, styles, classes, colour schemes, interactions and motion, take screenshots, lint pages, audit accessibility and SEO, manage global components and layouts, redirects, page versions and publishing. Form submissions and site analytics are read only.

cms

List collections and their field reference, create or change content types, search, create and update entries (also in bulk), link relations, set entry status, and list or restore entry versions.

commerce

Search, create and update products, variants, offers and channels, adjust prices and inventory, organise collections and taxonomies, create or disable discounts, and read orders, customers and sales analytics. Customer details are kept narrow (name and email, city and country).

code

Create and edit code components with small exact edits, browse their version history and restore versions, and create, read, write, screenshot and publish Code Builder projects. Approving an app's data access is never done by an assistant; that stays with a person in Code Builder.

design

Find Studio projects, read the open design's canvas, edit text, layers, photos, layout, motion and audio, manage scenes, take screenshots, export video, and push the result back to a linked social post after you confirm.

media

Find library items, upload images or any supported media file (directly, from a public link, or through an upload link for big files), generate images with Praisma's image model, edit, extend, upscale or vectorize images, and remove photo backgrounds. Generating images spends AI credits and needs your confirmation.

social

Make a post visual (from a script or a design template), file it in the media library and create a draft post. Read and triage the social inbox, and reply or moderate comments only after you approve the exact text. Read social analytics.

campaign and brand

Create and approve campaign plans and weeks, set briefs, budgets and featured products, run deliverables and read campaign metrics. Read and update brand kits and their assets.

workspace: skills

Skills are your workspace's own how-tos, styles and rules for AI, written once and followed by every assistant, in the app and over MCP. A skill has a name, an @slug, a “use this when” description, a category and a body. It applies in one of three ways:

Always: included in every conversation (keep these short).

Auto(default): the assistant sees the description and reads the body when a task matches.

Manual: used only when someone names it, for example@brand-voice.

Manage skills under Settings → Skills, or ask an assistant to save what you just did as a skill. Saving, editing or deleting a skill over MCP needs your confirmation, because it changes how every assistant behaves.

Not available over MCP

Creating, duplicating or deleting whole sites, and long-running AI jobs such as translating an entire site, are done in the app.