Skip to main content
Glama
PROMPTEYE-SP-Z-O-O

prompteye-mcp

Official
by PROMPTEYE-SP-Z-O-O
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Pause, resume, file or re-prioritise a prompt

update_prompt

Update a tracked prompt's status, group, category, or business priority in the active project, pausing or resuming it to manage plan capacity while keeping its history intact.

Instructions

Changes what happens to one prompt from here on in the active project: whether it is asked (status 'active' or 'paused'), which group and categories it is filed under, and how much the project bets on it.

Note:

  • Pausing a prompt frees capacity against the plan limit; resuming consumes capacity.

  • The prompt text itself cannot be changed: a different question is a different measurement (add a new prompt and pause the old one instead).

  • Moving a prompt between groups or categories keeps its history intact.

  • Setting businessPriority overrides the computed priority; passing null hands it back to PromptEye's computation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoWhether the prompt is asked on the next run ('active' or 'paused').
groupIdNoGroup id to move the prompt into, or null to leave it ungrouped.
promptIdYesId of the prompt to update, as list_prompts reports it.
categoryIdNoCategory id to file the prompt under, as listed by list_categories. Null clears all categories.
subcategoryIdNoSubcategory id of categoryId, which must be sent together with categoryId.
businessPriorityNoSets priority manually ('very_high', 'high', 'medium', 'low', 'very_low'), or null to reset to computed.
businessPriorityReasonNoReason why that priority was set manually.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.12

TDQS

A4.9/5.0
Behavior5/5

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

With only readOnlyHint=false and destructiveHint=false in annotations, the description carries the behavioral disclosure burden and handles it well. It explains capacity effects of pausing/resuming, history preservation on re-filing, and that businessPriority overrides computed priority while null returns control to PromptEye's computation. No annotation contradiction exists.

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?

The description is front-loaded with the core purpose and uses concise note bullets for caveats. Every sentence carries information and there is no filler or unnecessary repetition of the input schema.

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

Completeness5/5

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

For a 7-parameter mutation tool with no output schema, the description covers the key lifecycle effects, constraints on text editing, history preservation, priority semantics, and an alternative workflow. The only omission is the response shape, but the action-oriented nature and rich input documentation make this acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents each parameter. The description adds value beyond the schema by explaining the semantic consequences of businessPriority and the capacity implications of status changes, though it does not repeat every parameter interaction already covered by 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 opens with a specific verb and resource, 'Changes what happens to one prompt', and clearly enumerates the mutable dimensions: status, group/category filing, and priority. It distinguishes update_prompt from read/list/add siblings by stating it mutates an existing prompt rather than retrieving or creating one.

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

Usage Guidelines5/5

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

The description explicitly states what the tool is for and gives a clear exclusion: the prompt text cannot be edited, with the alternative being to add a new prompt and pause the old one. This gives an agent enough context to choose update_prompt over add_prompts or other siblings.

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