Skip to main content
Glama

migrate_prompt

Create or update prompts idempotently for CI/CD with app and environment metadata. Dry-run option enables safe preflight checks.

Instructions

Create or update a prompt in one idempotent step for CI/CD and prompt-as-code flows. Finds existing prompts by name within the collection, stores app/env in template_metadata, and supports dry_run for safe preflight checks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPrompt name to create or find for update
appYesApp identifier (REQUIRED). Use your deployed app name, for example 'hourlink' or 'support-console'.
envYesEnvironment identifier (REQUIRED). Use your environment name, for example 'dev', 'staging', 'prod', or 'qa'.
collection_idYesCollection ID to search in and create under
stringNoLegacy prompt template string with {{variable}} mustache syntax.
messagesNoStructured chat template alias for migrations. Serialized to the legacy string format before the prompt is created or updated.
parametersYesDefault values for template variables
virtual_keyYesVirtual key slug for model access
modelNoModel identifier
version_descriptionNoDescription for this version
template_metadataNoAdditional custom metadata
functionsNoFunction definitions
toolsNoTool definitions
tool_choiceNoTool choice strategy
dry_runNoWhen true, only check what action would be taken without making changes

Output Schema

TableJSON 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
Behavior2/5

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

The description adds context about idempotency, dry_run, and metadata storage, but contradicts the annotation idempotentHint=false by claiming the operation is idempotent.

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 sentences, front-loaded purpose, no fluff. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 15 parameters and an output schema, the description covers idempotency, dry_run, and metadata storage but omits relationships between string and messages, and how functions/tools work. Adequate but not complete.

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?

Input schema has 100% coverage, so baseline is 3. The description reiterates some parameters (dry_run, template_metadata) but does not add significant new meaning beyond the schema.

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?

The description clearly states the tool creates or updates a prompt in an idempotent step for CI/CD flows, distinguishing it from siblings like create_prompt and update_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?

The description specifies it is for CI/CD and prompt-as-code flows and mentions dry_run for preflight checks, but does not explicitly contrast with sibling tools or state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/s-b-e-n-s-o-n/portkey-admin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server