Skip to main content
Glama

create_prompt

Register a new prompt template with a unique name and version. Prevents duplicates by returning a 409 conflict. Enables AI agents to auto-register templates for evaluations and experiments.

Instructions

Register one new prompt template (Pro+ only). name + version + template are required; variables / labels / description are optional. An existing (name, version) pair returns 409 (UNIQUE constraint). Used when an AI agent auto-registers templates for dogfood evals / experiments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPrompt name (series identifier, [A-Za-z0-9][A-Za-z0-9_-]{0,63}). E.g. 'customer_support'
labelsNoArray of labels (up to 8, each [A-Za-z0-9][A-Za-z0-9_-]{0,31}). E.g. ['production', 'staging'].
versionYesVersion identifier ([A-Za-z0-9][A-Za-z0-9._-]{0,63}). E.g. 'v1' / '1.0.2' / '2026-06-03'
templateYesPrompt body (non-empty, up to 50000 chars). {{var}} placeholders are filled from variables.
variablesNoDefault values for {{var}} placeholders in the template (plain object, 4096 bytes max after JSON serialization). Optional.
descriptionNoDescription (up to 500 chars). Optional.
Behavior3/5

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

No annotations, so description carries full burden. Discloses unique constraint (409 error) and Pro+ restriction. Does not mention auth needs, rate limits, or response format. Adequate but not exhaustive.

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 concise sentences with purpose front-loaded. No filler, but could be slightly more structured (e.g., bullet points for use cases). Efficient overall.

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?

Given 6 params, no output schema, and schema covering all fields, the description is fairly complete. Covers required fields, duplicate behavior, and use case. Missing return value description is acceptable without output schema.

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 100% with descriptions. Description adds no extra semantics beyond restating required/optional fields. Baseline score 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?

Description clearly states the tool registers a new prompt template (Pro+ only). It specifies required and optional fields, and mentions auto-registration for dogfood evals/experiments, distinguishing it from siblings like update_prompt and delete_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?

Provides context: 'Used when an AI agent auto-registers templates for dogfood evals / experiments' and warns about duplicate (name, version) returning 409. Does not explicitly list alternatives but context implies creating vs updating.

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/argosvix/mcp-server'

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