Pretty Prompt MCP Server

move_prompt_to_folder

Organize prompts by moving them into folders or back to the library root. Specify destination folder ID or set null to clear the folder.

Instructions

Move a library prompt into a folder, or to the library root. Call list_library_folders first to resolve folder UUIDs. Pass folder_id=null to remove the prompt from its folder.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt_id": "<prompt_id>"
    },
    "name": "move_prompt_to_folder"
  }
}

Input Schema

Name	Required	Description	Default
`folder_id`	No	Destination folder UUID, or null for root
`prompt_id`	Yes	Library prompt ID (from list_library_prompts)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It clearly discloses the state-changing behavior: moving a prompt to a folder or root, and removing it from a folder with folder_id=null. This is transparent about the operation's effect, though it doesn't detail error cases or side effects beyond the move.

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 concise sentences with the primary action front-loaded. Every clause adds value: the move action, the prerequisite, and the special null behavior. No wasted words and no repetition of schema details.

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 simple two-parameter tool with no annotations and no output schema, the description covers the essential behavior, the key edge case (null), and the necessary precursor step. It is complete enough for an agent to select and invoke the tool correctly without further documentation.

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% with both parameters described, giving a baseline of 3. The description adds value by clarifying the null semantics for folder_id ('remove the prompt from its folder') and the prerequisite to call list_library_folders, which enriches the meaning beyond the schema's field 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 the action: 'Move a library prompt into a folder, or to the library root.' It uses a specific verb ('Move') and resource ('library prompt'), and distinguishes itself from siblings like list_library_prompts and save_to_library by focusing on organization rather than creation or listing.

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 explicit prerequisite guidance: 'Call list_library_folders first to resolve folder UUIDs.' It also explains when to use folder_id=null. While it doesn't explicitly mention when not to use this tool versus alternatives, the context is clear that this is for moving existing prompts, not for saving new ones.

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

Deploy Server