Skip to main content
Glama

Update demo details

update_demo
DestructiveIdempotent

Changes a demo’s title, description (shown under the title on the hosted page), share settings, brand kit (themeId from list_workspaces), folder, access or link (slug: /d/). Saved to the draft and to revision history; title, description and theme reach viewers on the next publish_demo, settings, access and the link apply at once (earlier links keep working). Changing access also needs demos:publish.

Requires: demos:read, demos:write.

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": {
      "demoId": "<demoId>"
    },
    "name": "update_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoThe demo’s link, /d/<slug> and /embed/<slug>: 3–48 lowercase letters, digits or hyphens, unique across AtriumKit. Earlier links (and personalized links) keep working.
titleNo
accessNopublic, unlisted (link only, not indexed) or email (email gate, Pro).
demoIdYesDemo id (from list_demos), e.g. "d_Ab12Cd34Ef56Gh78".
themeIdNoBrand kit id, or null for the workspace default.
folderIdNoFolder id, or null for no folder.
settingsNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / settings / properties / cta
      Added value: +{
      +  "description": "A call-to-action button that stays in the player, embeds included (every plan), sent whole.",
      +  "properties": {
      +    "after": {
      +      "maximum": 200,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "label": {
      +      "anyOf": [
      +        {
      +          "maxLength": 40,
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Button text; null: the brand kit’s header button text."
      +    },
      +    "on": {
      +      "type": "boolean"
      +    },
      +    "popup": {
      +      "description": "Calendly, Chili Piper, HubSpot, Cal.com and SavvyCal links open in a popup over the demo.",
      +      "type": "boolean"
      +    },
      +    "show": {
      +      "description": "From the start, from step `after` (clickable: the Nth screen opened), or at the end.",
      +      "enum": [
      +        "always",
      +        "after",
      +        "end"
      +      ],
      +      "type": "string"
      +    },
      +    "style": {
      +      "enum": [
      +        "button",
      +        "pill"
      +      ],
      +      "type": "string"
      +    },
      +    "url": {
      +      "anyOf": [
      +        {
      +          "maxLength": 2048,
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "https:, mailto: or tel: link (variables allowed after the host, or {{rep.calendar|https://…}}); null: the brand kit’s."
      +    }
      +  },
      +  "required": [
      +    "on",
      +    "label",
      +    "url",
      +    "style",
      +    "show",
      +    "after",
      +    "popup"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / settings / properties / hostEvents
      Added value: +{
      +  "description": "Player events for the embedding page (Pro), sent whole.",
      +  "properties": {
      +    "identifyOrigins": {
      +      "description": "Sites like https://www.example.com whose pages get the viewer’s email with lead_captured.",
      +      "items": {
      +        "maxLength": 200,
      +        "type": "string"
      +      },
      +      "maxItems": 20,
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "identifyOrigins"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / settings / properties / leadForm
      Added value: +{
      +  "description": "Lead form rules (Pro), sent whole.",
      +  "properties": {
      +    "allowSkip": {
      +      "description": "Lead form steps and the before-the-last-step ask show Skip (never the email gate).",
      +      "type": "boolean"
      +    },
      +    "blockedDomains": {
      +      "description": "Domains to refuse, e.g. [\"acme.com\"] (subdomains too).",
      +      "items": {
      +        "maxLength": 260,
      +        "type": "string"
      +      },
      +      "maxItems": 200,
      +      "type": "array"
      +    },
      +    "endFields": {
      +      "description": "Fields of the before-the-last-step ask, as a form step’s `form` (absent: the email only).",
      +      "items": {
      +        "additionalProperties": {},
      +        "propertyNames": {
      +          "type": "string"
      +        },
      +        "type": "object"
      +      },
      +      "maxItems": 20,
      +      "type": "array"
      +    },
      +    "rememberDays": {
      +      "description": "Remember a viewer who left their details on their device for this many days (0: this visit only).",
      +      "maximum": 90,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "returning": {
      +      "description": "A remembered viewer skips the forms, or gets them filled in.",
      +      "enum": [
      +        "skip",
      +        "prefill"
      +      ],
      +      "type": "string"
      +    },
      +    "workEmail": {
      +      "description": "Refuse free email providers (Gmail, Outlook…).",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "workEmail",
      +    "blockedDomains",
      +    "allowSkip",
      +    "rememberDays",
      +    "returning"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / settings / properties / phone
      Added value: +{
      +  "description": "How phones show it: layout (default: the screen follows each step at a readable size, text in a bottom sheet), stories (one full-screen card per step to tap or swipe through) or desktop (the desktop player scaled down); fullscreen: embeds on phones open full screen from a poster.",
      +  "properties": {
      +    "fullscreen": {
      +      "type": "boolean"
      +    },
      +    "mode": {
      +      "enum": [
      +        "layout",
      +        "stories",
      +        "desktop"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / slug
      Added value: +{
      +  "description": "The demo’s link, /d/<slug> and /embed/<slug>: 3–48 lowercase letters, digits or hyphens, unique across AtriumKit. Earlier links (and personalized links) keep working.",
      +  "maxLength": 48,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare a destructive, idempotent write; the description adds context annotations cannot: edits are saved to the draft and to revision history (implying recoverability), some fields are staged until publish while others take effect at once, and 'earlier links keep working' after a slug change. The added permission requirement for `access` is exactly the kind of auth detail annotations cannot express.

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?

Front-loaded with the field list, then behavior/propagation, then permission requirements — a sensible ordering with no filler sentences. It is dense and long, but nearly every clause carries information the agent needs; only the nested-parenthetical style makes it slightly harder to scan.

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 an eight-parameter, deeply nested, destructive mutation with no output schema, the definition covers propagation timing, history/draft state, permission prerequisites and field provenance. The remaining gap is what happens to fields omitted from the call and what the response contains, which matters for a partial update tool.

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?

With schema coverage at 63% and a deep nested `settings` object, the description still contributes meaning: description text is 'shown under the title on the hosted page', themeId resolves via list_workspaces, slug maps to /d/<slug>, and access changes carry an extra scope. It does not explain partial-update semantics for the eight optional parameters, which is the notable omission.

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 ('Changes a demo's') and enumerates the exact mutable surfaces: title, description, share settings, brand kit, folder, access and link. It even disambiguates scope by naming sibling tools where relevant (themeId from list_workspaces, deferral to publish_demo, step-level fields in update_step), so an agent can separate it from update_content/update_scene without opening a schema.

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

Usage Guidelines4/5

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

Tells the agent how changes propagate: title/description/theme land on the next publish_demo, while settings/access/link apply immediately, which is the key decision input for sequencing calls. It also names the required scopes (demos:read, demos:write, plus demos:publish when changing access). What it does not state is the explicit when-not-to-use case (e.g., use update_content/update_scene for screen-level edits), leaving one gap.

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.