Skip to main content
Glama

List prompt topics

list-prompt-topics
Read-only

List a domain's prompt topics, sorted by name, with id, name and description. The id is the topic_id that get-visibility-score, move-prompt-to-topic, update-prompt-topic and delete-prompt-topic take.

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": {
      "domain_id": "<domain_id>"
    },
    "name": "list-prompt-topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_idYesDomain ID from list-domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain_id / description
      Previous value: -"Domain ID"New value: +"Domain ID from list-domains"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domain_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower; the description still adds real value by disclosing the sort order and the returned field set. With no output schema present, that return-shape disclosure is genuinely useful. It does not mention pagination, result limits, or empty-result behavior for a domain with no topics.

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 tight sentences, no filler. The core action and return shape come first, and the downstream-id guidance follows as the secondary fact an agent needs.

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 one-parameter read tool with no output schema, the description adequately covers action, ordering, returned fields, and cross-tool linkage. Minor gaps remain around whether results are paginated or unbounded and what an empty domain returns.

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?

Only one parameter exists and schema coverage is 100% — the schema already documents domain_id as a UUID sourced from list-domains. The description refers to "a domain's" topics but adds no format, sourcing, or constraint detail beyond the schema. 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 a domain's prompt topics") plus the scope (a single domain), the sort order (by name), and the exact fields returned (id, name, description). It also distinguishes itself from write-side siblings like create-prompt-topic by naming the consumers of the returned topic_id.

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?

The second sentence tells the agent precisely when this tool is needed: to obtain the topic_id required by get-visibility-score, move-prompt-to-topic, update-prompt-topic and delete-prompt-topic. That is a clear usage trigger. It stops short of an explicit when-not or a comparison against list-prompt-filters, so it is not a full 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources