Skip to main content
Glama

agentlens_prompts

Manage AI prompt templates and versions. List, create, update, track analytics, and discover prompt fingerprints for your agents.

Instructions

Manage prompt templates and versions.

Actions:

  • list: List prompt templates (optional category, search filters)

  • get: Get a template with all versions by ID

  • create: Create a new prompt template with initial content

  • update: Create a new version of an existing template

  • analytics: Get per-version metrics for a template

  • fingerprints: List auto-discovered prompt fingerprints

Example: agentlens_prompts({ action: "list", category: "system" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform
templateIdNoTemplate ID (for get, update, analytics)
nameNoTemplate name (for create)
contentNoPrompt content (for create, update)
descriptionNoTemplate description (for create)
categoryNoCategory filter or value
variablesNoJSON array of variable definitions (for create)
changelogNoChange description (for update)
searchNoName search filter (for list)
fromNoStart date ISO (for analytics)
toNoEnd date ISO (for analytics)
agentIdNoAgent ID filter (for fingerprints)
Behavior2/5

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

The description lacks behavioral details beyond action names. No annotations are provided, so the description should disclose side effects, permissions, or behavior (e.g., what 'create' returns, whether updates are versioned). It only briefly mentions 'auto-discovered prompt fingerprints' without elaboration.

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?

The description is concise, well-structured with a header, bullet actions, and an example. It is front-loaded with purpose. However, the action list could be more compactly described.

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

Completeness2/5

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

Given 12 parameters and 6 actions, the description lacks detail for each action (e.g., return values, metric definitions). No output schema. Missing complete behavior for 'create', 'update', 'analytics', and 'fingerprints'.

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 is 100% and each parameter has a description indicating which actions it applies to. The tool description echoes this with a list, but adds no additional semantics like constraints, defaults, or usage examples. Baseline 3 is appropriate.

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?

The description clearly states the tool manages prompt templates and versions, and lists specific actions. However, it does not differentiate from sibling tools like agentlens_agents or agentlens_context, lacking sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. The description lists actions but does not provide context or prerequisites for choosing this tool over sibling prompt-related tools.

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/agentkitai/agentlens'

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