Skip to main content
Glama
MCP Prompts Server

MCP Prompts Server

by sparesparrow

List prompts

list_prompts
Read-onlyIdempotent

Lists available prompts with summaries and filters by tags, category, template status, or search text; supports pagination for browsing and locating prompts before retrieving full content.

Instructions

List the prompts this server serves, as summaries (id, name, description, tags, isTemplate, category, version, language). Filter with tags (any match), category, isTemplate and search (name, description and content). Returns up to limit prompts starting at offset; when has_more is true, call again with offset = next_offset. Use get_prompt for the content of one prompt.

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

NameRequiredDescriptionDefault
tagsNoReturn prompts carrying any of these tags
limitNoMost prompts to return (1-100, default 50)
offsetNoPrompts to skip; use next_offset from the previous page
searchNoText to look for in the name, description or content (case-insensitive)
categoryNoReturn prompts of this category, e.g. "embedded" (get_stats lists the categories)
isTemplateNotrue for templates only, false for plain prompts only

Output Schema

NameRequiredDescriptionDefault
countYesPrompts in this page
limitYes
totalYesPrompts matching the filter
offsetYes
promptsYes
has_moreYes
next_offsetNoOffset of the next page; present when has_more is true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv4.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "Return prompts of this category, e.g. \"embedded\" (get_stats lists the categories)",
      +  "type": "string"
      +}
    • addedInput schema / properties / isTemplate
      Added value: +{
      +  "description": "true for templates only, false for plain prompts only",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 50,
      +  "description": "Most prompts to return (1-100, default 50)",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Prompts to skip; use next_offset from the previous page",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / search / description
      Previous value: -"Text to look for in the name, description or content"New value: +"Text to look for in the name, description or content (case-insensitive)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "count": {
      +      "description": "Prompts in this page",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "has_more": {
      +      "type": "boolean"
      +    },
      +    "limit": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "next_offset": {
      +      "description": "Offset of the next page; present when has_more is true",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "offset": {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "prompts": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "category": {
      +            "type": "string"
      +          },
      +          "createdAt": {
      +            "type": "string"
      +          },
      +          "description": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "isTemplate": {
      +            "type": "boolean"
      +          },
      +          "language": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "tags": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "version": {
      +            "type": [
      +              "number",
      +              "string"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "description",
      +          "tags",
      +          "isTemplate",
      +          "createdAt",
      +          "version"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "description": "Prompts matching the filter",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "count",
      +    "offset",
      +    "limit",
      +    "has_more",
      +    "prompts"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changedv4.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv4.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds non-obvious behavior beyond that: results are summaries not full records, tags filter is any-match, search spans name/description/content, and the paging contract via has_more/next_offset.

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?

Four tight sentences ordered by importance: what it returns, how to filter, how to page, and where to go for full content. No filler or restatement of the name/title.

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 six-parameter, optional-only filtered list tool with an output schema, everything an agent needs is present: filter semantics, page size/continuation, the summary field set, and sibling routing. Return-value detail is legitimately left to the output schema.

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 the schema already documents tags as any-match, search over name/description/content, the limit range, the offset continuation rule, and that get_stats lists categories. The description mostly mirrors those semantics, adding only the framing of the pagination loop, so the baseline 3 is appropriate.

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?

States a specific verb and resource ("List the prompts this server serves") and immediately scopes the result shape to summaries with an explicit field list. It distinguishes itself from the sibling that fetches full content by naming get_prompt directly.

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?

Gives the positive case (browse/filter prompts) and the alternative ("Use get_prompt for the content of one prompt"), plus a secondary pointer to get_stats for discovering category values. It also tells the agent how to continue: when has_more is true, call again with offset = next_offset.

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