Skip to main content
Glama
avivsinai

langfuse-mcp

create_text_prompt

Create a new version of a text prompt to update its content in Langfuse. Supports variables, labels, and config for LLM applications.

Instructions

Create a new text prompt version in Langfuse.

Prompts are immutable; creating a new version is the only way to update prompt content. Labels are unique across versions - assigning a label here will move it from other versions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the prompt to create
promptYesPrompt text content (supports {{variables}})
labelsNoLabels to assign (e.g., ['production', 'staging'])
configNoOptional JSON config (e.g., {model: 'gpt-4', temperature: 0.7})
tagsNoOptional tags for organization (e.g., ['experimental', 'v2'])
commit_messageNoOptional commit message describing the changes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description discloses immutability and that labels move between versions, which are key behavioral traits. However, it could elaborate on side effects or prerequisites.

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?

Three concise sentences with no wasted words. Every sentence provides essential context: creation, immutability, and label behavior.

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 description covers purpose and key behaviors. It does not mention that the prompt name must already exist (if that is a prerequisite), but with an output schema present, return values are covered.

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 the schema already documents all 6 parameters. The description adds no extra meaning beyond the schema's descriptions.

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 'Create a new text prompt version in Langfuse' with a specific verb and resource, and the name 'create_text_prompt' distinguishes it from sibling like 'create_chat_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?

It explains immutability and label uniqueness, guiding when to use (to update content) and warning about label movement, but does not explicitly mention alternatives like 'update_prompt_labels'.

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/avivsinai/landfuse-mcp'

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