Skip to main content
Glama

promote_prompt

Copies a prompt from one environment to another and automatically creates or updates the target for staged releases, returning source and target version IDs.

Instructions

Copy a prompt from one environment to another and create or update the target automatically. Use this for staged releases when you want the target prompt synchronized without manual edits, and it returns both source and target version ids.

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": {
      "source_prompt_id": "<source_prompt_id>",
      "target_collection_id": "<target_collection_id>",
      "target_env": "<target_env>"
    },
    "name": "promote_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_envYesEnvironment identifier (REQUIRED). Use your environment name, for example 'dev', 'staging', 'prod', or 'qa'.
target_nameNoTarget prompt name (defaults to source name with env suffix replaced)
virtual_keyNoVirtual key ID to use (defaults to source prompt's virtual_key)
source_prompt_idYesSource prompt ID or slug (e.g., staging prompt)
target_collection_idYesTarget collection ID for the promoted prompt

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

A3.6/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds genuinely useful behavior beyond that: the target is created-or-updated automatically, and both source and target version ids are returned. It does not say whether an existing target's content is overwritten, whether auth on the target environment is required, or what happens when the target does not exist.

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?

Two sentences, front-loaded with the core action, with no filler. The closing clause about returning source and target version ids slightly duplicates what the existing output schema already conveys, but it is not enough to harm readability.

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 annotations, a fully described 5-parameter schema, and an output schema covering return values, the description only needs to establish purpose and usage, which it does. Remaining gaps are edge-case behavior such as overwrite semantics and target authorization rather than anything essential to invoking the tool.

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% and all five parameters carry their own descriptions, including defaults for target_name and virtual_key, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond what the schema states, which is the expected baseline here.

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?

Names a specific verb (copy/promote) and resource (prompt), plus the scope of moving between environments and auto-creating or updating the target. It is clear what the tool does, but with a sibling named migrate_prompt in the catalog, the description never distinguishes the two, leaving an agent to guess which is appropriate.

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?

Gives a concrete usage context: 'use this for staged releases when you want the target prompt synchronized without manual edits.' That is enough context to recognize the intended scenario, but there are no explicit exclusions or pointers to alternatives such as migrate_prompt or update_prompt.

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