Skip to main content
Glama

List prompts

list_prompts
Read-onlyIdempotent

Lists read-only Prompts Studio library entries so you can inspect available prompts, optionally scoped to a workspace and limited by row count.

Instructions

List Prompts Studio library entries. Use import_studio_pack to add prompts, and get_studio_entity for one row. Read-only. Returns JSON items up to limit.

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
limitNoMaximum rows. Integer from 1 to 500. Default 100.
workspaceNoOptional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.3.0
    • addedInput schema / properties / workspace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.",
      +  "title": "Workspace"
      +}
  2. Changed1 schema field changedv6.2.1
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows. Integer from 1 to 500. Default 100."
  3. Addedv6.1.5

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description's 'Read-only' line restates structured data. The only added behavior is that results are JSON items capped by the limit, which the output schema likely covers anyway. Useful but minimal beyond structured fields.

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?

Three short sentences, front-loaded with the purpose before the alternatives. The 'Read-only' and 'Returns JSON items' clauses are largely redundant with annotations and the output schema, costing a little tightness.

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

Completeness4/5

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

For a simple two-parameter read tool with full schema coverage, complete annotations, and an output schema, the description covers purpose, alternatives, and output shape. Nothing essential is missing, though workspace scoping is left entirely to the 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 description coverage is 100%, with both limit (1-500, default 100) and workspace (name/slug/id, defaults to active workspace) fully documented in the schema. The description only references the limit cap and adds no syntax or semantics beyond that, so baseline 3 applies.

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 Prompts Studio library entries') and explicitly separates itself from import_studio_pack (adding) and get_studio_entity (single row). An agent can pick this tool over its named siblings without opening a schema.

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?

Gives concrete routing rules: use import_studio_pack to add prompts and get_studio_entity for one row, implying this tool is for bulk retrieval. It stops short of stating when this list is the wrong choice (e.g. other list_* domains), but the guidance present is explicit and actionable.

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