keepmyprompts-mcp

List saved prompts

list_prompts

Read-only

List the titles of your saved prompts with their categories, so you can locate and reuse or adapt a prompt from your library.

Instructions

List the titles of the user's saved prompts in Keep My Prompts, with their category. Call this when the user refers to a prompt of theirs, asks what is in their library, or asks you to reuse or adapt something they saved. Returns titles only — call get_prompt for the text of the one you need.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_prompts"
  }
}

Input Schema

Name	Required	Description	Default
`category`	No	Only list prompts in this category. Omit to list every prompt.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is known. The description adds important behavioral context: it returns titles only, not the full text, and includes category information. This goes beyond the annotations and helps set expectations.

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 sentences, each earning its place: purpose, usage, and a limitation with an alternative. No redundant phrasing or filler, making it efficient and easy to parse.

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 list tool with one optional parameter and no output schema, the description is complete. It covers what is returned, when to use it, and what to use for full text. The sibling tool context is also clear, so an agent can select this tool confidently.

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?

The schema already fully describes the single 'category' parameter with 100% coverage, so the description need not repeat it. The description adds marginal value by mentioning 'with their category' in the output, but the parameter semantics are adequately handled 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 clearly states the tool lists titles of saved prompts with their category, using a specific verb ('List') and resource. It distinguishes itself from get_prompt (which returns full text) and implicitly from list_categories (which likely lists categories), making the purpose unambiguous.

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?

Explicit when-to-use guidance is provided: when the user refers to their prompts, asks about their library, or wants to reuse/adapt something. It also gives an alternative instruction ('call get_prompt for the text'), clarifying when not to rely on this tool.

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

Deploy Server