Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

promote_prompt

Copies a prompt between environments and automatically creates or updates the target, keeping staged releases synchronized without manual edits.

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.

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
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Addedv1.0.1
  3. Removed
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already disclose mutation (readOnlyHint=false), non-idempotence, non-destructiveness, and open-world behavior. The description adds that the target is automatically created or updated and that source/target version ids are returned, but does not mention permissions or other side effects beyond the annotated safety profile.

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 copy/create-or-update action and followed by a use-case/return note. No redundant restatement of the title or schema, though the second sentence packs two distinct ideas together.

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?

The tool has annotations and an output schema, and the description adds the staged-release context and automatic target handling that an agent needs for selection. It omits authorization or permission requirements, but otherwise is complete enough for a copy-style mutation 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%, so all five parameters are documented in the schema itself. The description adds no parameter-level meaning beyond the schema; its mention of source and target version ids refers to return values, not input semantics.

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 (copy) and resource (prompt) across environments, and clearly says the target is created or updated. It distinguishes itself somewhat through the staged-release framing, but does not explicitly name sibling alternatives like migrate_prompt.

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 clear when-to-use context: staged releases where the target should be synchronized without manual edits. It does not provide explicit exclusions or name an alternative tool such as migrate_prompt, so it falls short of a full 5.

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