Skip to main content
Glama

Create a Stick site

create_site

Creates the owner's Stick site as an unpublished draft from a theme and blocks listed top to bottom, and returns its editor link. An account has one site: when it already has one, nothing is created and update_site changes it. The format is in get_guide: the draft as the editor stores it. Each block is { id, type, props } with an id of its own, unique in the site, and a text block's content is the JSON string of its Tiptap document. A props field left out takes its default: empty text, the first layout, no image; props may be {}. stickers is [] when there are none. If anything is invalid, nothing is created and every problem is listed. name is the owner's name for the site in Stick and also becomes the published page's title, which the owner can change under SEO. When images help the design, create native photo placeholders without image URLs, then use upload_images and update_site to fill them. Image-free designs need no upload.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "themeId": "<themeId>",
      "blocks": "<blocks>",
      "stickers": "<stickers>",
      "name": "<name>"
    },
    "name": "create_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
blocksYesTop to bottom
themeIdYes
stickersYesThe decorative GIPHY sticker layer; [] for none.
fontFamilyNo
websiteBgColorNo
websiteBgImageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (non-read-only, non-destructive, non-idempotent), it discloses that creation is atomic ('If anything is invalid, nothing is created and every problem is listed') and that the result is an unpublished draft with an editor link returned. It also flags the side effect that name becomes the published page title, editable under SEO. It does not mention permission or quota requirements, though the one-site rule already clarifies the non-idempotent behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core action, uniqueness rule, and return value are front-loaded, and nearly every sentence adds a distinct fact (format pointer, block shape, defaults, validation behavior, image workflow). Some sentences are long and clause-heavy, and the image-placeholder advice could be compressed, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create tool with no output schema, it covers creation semantics, atomic failure behavior, return value (editor link), the format source (get_guide), and the image follow-up path. Gaps: no mention of the optional styling parameters or of how the draft transitions to a published page. Annotations already cover the safety profile, so this is close to sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 29%, so the description must carry weight, and it does for the complex parts: block objects are { id, type, props } with site-unique ids, a text block's content is the JSON string of its Tiptap document, omitted props take defaults (empty text, first layout, no image), props may be {}, and stickers is [] when empty. name gains real meaning (Stick-internal name that also becomes the published title). However fontFamily, websiteBgColor and websiteBgImage receive no mention at all, leaving three of seven parameters unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource plus material scope: 'Creates the owner's Stick site as an unpublished draft from a theme and blocks listed top to bottom, and returns its editor link.' It explicitly distinguishes itself from update_site ('An account has one site: when it already has one, nothing is created and update_site changes it'), so an agent can route between the two siblings without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use and when-not-to-use rule keyed to the one-site-per-account constraint, and names the alternative (update_site) for the already-exists case. It also routes to get_guide for the payload format and prescribes a follow-up workflow (create photo placeholders, then upload_images + update_site) for image-bearing designs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources