Skip to main content
Glama

Publish blog design

publish_design
Destructive

Make all supported native settings and custom CSS from the current Design Studio draft live. Requires explicit user intent to publish. Read get_design and review the draft first; use its exact revision. Includes native edits saved in the UI. Preserves other pending Studio changes; a pending theme switch must be published in Design Studio first.

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": {
      "revision": "<revision>"
    },
    "name": "publish_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYesExact quoted design revision.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotent, so the safety profile is carried by structured data. The description adds genuine context beyond that: what exactly goes live, that other pending Studio changes are preserved, and the theme-switch exception. It does not state whether the publish can be reverted, which is the remaining gap for a destructive operation.

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

Conciseness5/5

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

The action is front-loaded in the first sentence, followed by prerequisites, sourcing instructions, and finally an exception. No sentence is redundant despite the density, and the semicolons keep related preconditions grouped.

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 one-parameter destructive tool with no output schema, the description covers scope, prerequisites, and side-effect boundaries well. It is slightly incomplete on post-publish behavior — what the call returns and how a mistaken publish is undone — which matters given destructiveHint=true.

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 100% and the single revision parameter is already documented as 'Exact quoted design revision'. The description still adds provenance meaning the schema lacks: the revision must come from a prior get_design review and be used exactly, which tells the agent how to obtain and handle the value.

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?

States a specific verb (make live) and a precise resource scope: native settings plus custom CSS from the current Design Studio draft. The Design Studio framing plus 'custom CSS' separates it cleanly from content-publishing siblings such as publish_content without needing to name them.

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 prerequisite chain (requires explicit user intent, read get_design and review the draft first, use its exact revision) and a blocking condition (a pending theme switch must be published in Design Studio first). An agent knows both when to call it and when to stop and do something else.

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