Skip to main content
Glama

publish_prompt

Sets a specific prompt version as the active default, immediately routing all slug callers to it. Verify the version first because this action has no rollback.

Instructions

Publish a specific version of a prompt as the active default, unlike promote_prompt which copies across environments or update_prompt which creates a new draft. This immediately routes all callers using the slug to that version and there is no rollback, so use list_prompt_versions to pick the version and update_prompt first if you need to create new content before promoting it.

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": {
      "prompt_id": "<prompt_id>",
      "version": "<version>"
    },
    "name": "publish_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesVersion number to publish as the default
prompt_idYesPrompt ID or slug to publish

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv1.0.1
  4. Removed
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: publishing immediately reroutes all callers using the slug, and there is no rollback. That irreversibility notice is the key operational fact an agent needs and is not in the structured fields. Minor tension with destructiveHint=false, since an unrollbackable overwrite of the active default has a destructive flavor, but publishing the alias itself is not data deletion, so it does not rise to an outright contradiction.

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 core action, then sibling differentiation, then the irreversibility warning, then prerequisites — a logical ordering with no filler. Slightly dense packing of four distinct facts into two sentences costs it the top score.

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?

Output schema exists, so return values need not be explained; parameter docs are complete in the schema. The description covers the mutation's blast radius, irreversibility, and prerequisites, which is most of what matters for a publish operation. It could still note whether republishing the same version is a no-op given idempotentHint=false, but overall it is sufficient.

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 description coverage is 100%, so both parameters are already documented ('Version number to publish as the default', 'Prompt ID or slug to publish'). The description adds only the procedural hint that versions should be sourced from list_prompt_versions, not new syntax or constraint meaning. Baseline 3 is appropriate.

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 and resource ('Publish a specific version of a prompt as the active default') and immediately contrasts it with two named siblings, promote_prompt (cross-environment copy) and update_prompt (new draft). An agent can distinguish this from every plausible alternative 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 Guidelines5/5

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

Explicit about the precondition-to-action sequence: use list_prompt_versions to choose a version and update_prompt first if new content must be created. When-not guidance is implied by the sibling contrasts (don't use this to copy environments or to author content), leaving little to inference.

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

Deploy Server

Other Tools