Skip to main content
Glama

publish_style

Freeze the current draft of a style as a new version and return its URLs: the versioned one never changes, the latest one follows future publishes within five minutes. Owner or admin.

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": {
      "style_id": "<style_id>"
    },
    "name": "publish_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
style_idYesThe style's id (uuid).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes beyond the annotations by explaining that the versioned URL is immutable and the latest URL trails publishes by up to five minutes, plus the owner/admin authorization requirement. The snapshot-per-call behavior usefully corroborates the non-idempotent hint, though it never states outright that repeated calls create additional versions.

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?

One sentence, front-loaded with the core action, with the colon-delimited clause efficiently covering both returned URL semantics. Every clause carries information an agent needs; nothing is padding.

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?

With no output schema, the description correctly covers the return shape (two URLs and their differing stability) along with auth and propagation timing. It is nearly complete for a one-parameter mutation; the only gap is behavior when the draft is unchanged or already published.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter is documented in-schema as a uuid, so baseline is 3. The description refers to 'a style' but adds no syntax or source details beyond the schema.

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

Purpose4/5

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

States a specific verb and effect ('Freeze the current draft of a style as a new version') plus what it returns ('its URLs'), which clearly separates it from update_style's editing role. It never names the sibling it is distinguished from, so the differentiation is inferred rather than explicit.

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

Usage Guidelines3/5

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

The permission gate ('Owner or admin') is stated, which tells the agent a precondition for invoking. However, there is no explicit guidance on when to publish versus when to modify the draft with update_style, and no mention of what happens on a repeat publish with no changes.

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