Skip to main content
Glama

update_prompt_version

Destructive

Assign or remove a label on a specific prompt version by prompt ID and version UUID; use null to clear the label after looking up IDs with list_prompt_labels.

Instructions

Update a specific prompt version's label assignment. This only assigns or removes a label, and null clears the label after you look up ids with list_prompt_labels.

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_id": "<version_id>",
      "label_id": "<label_id>"
    },
    "name": "update_prompt_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
label_idYesLabel ID to assign to this version, or null to remove the label
prompt_idYesPrompt ID or slug
version_idYesVersion UUID to update

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. Changed2 schema fields changedv0.12.2
    • removedInput schema / properties / label_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / label_id / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  4. Addedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

The annotations declare destructiveHint=true and idempotentHint=false; the description's key contribution is constraining that destructiveness to "only assigns or removes a label," reassuring the agent it will not delete the version itself. It adds nothing about permissions, whether an existing label is replaced or coexists, or what the openWorldHint=true implies. The scope constraint is useful but the disclosure is thin.

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?

Two tight sentences with the scope constraint front-loaded before the null-handling detail. Every clause carries information and nothing is redundant.

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?

An output schema exists, so return values need no explanation, and the description covers the one non-obvious behavioral fact (label-only, null removes). The main residual gap is whether a version may hold several labels or whether assignment replaces an existing one, which matters for a non-idempotent destructive call.

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%, with label_id's null behavior and the prompt_id slug alternative already documented in the schema, so the description is largely restating structured data. The list_prompt_labels pointer for obtaining label_id adds minor value beyond the schema but does not change how the parameters are interpreted.

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?

The description names a specific verb and resource ("Update a specific prompt version's label assignment") and immediately narrows the scope with "This only assigns or removes a label," which separates it from broader siblings like update_prompt and update_prompt_label. It stops short of explicitly naming which sibling to use for other kinds of prompt-version edits, so it lands at 4 rather than 5.

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?

It gives concrete operational guidance: null clears the label, and ids must be resolved first via list_prompt_labels, which is a genuine prerequisite that routes the agent to the right sibling. There is no explicit "do not use this when..." clause or comparison against update_prompt_label, so the exclusion side is left implicit.

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