Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_prompt_topics

Retrieve prompt topics with their IDs and titles to organize prompts on the Prompt Tracking page, then use a topic ID when creating or updating prompts.

Instructions

List the prompt topics that group prompts on the Prompt Tracking page — each with topic_id and title. Pass a topic to create_prompt / update_prompt to file a prompt under it.

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_prompt_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden itself; 'List' implies a read-only, non-mutating call, and it discloses the return shape (topic_id and title), which is useful since there is no output schema. It says nothing about ordering, pagination, or whether topics with no prompts are included.

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 short sentences, zero filler. The core identification comes first, followed by the practical follow-up action, which is the right front-loading for a trivial lookup tool.

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 zero-parameter list tool with no annotations and no output schema, the description covers purpose, returned fields, and downstream usage — enough to call it correctly. Only secondary details like ordering or result limits are absent, which is a minor gap at this complexity level.

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?

The tool takes zero parameters and the schema is an open object, so there is no parameter semantics to convey. The description correctly adds no parameter discussion and instead explains how the returned topic_id is consumed elsewhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 prompt topics that group prompts on the Prompt Tracking page') and even names the returned fields, topic_id and title, so an agent knows exactly what it gets back. It is clearly not create_prompt_topic or delete_prompt_topic, though it doesn't explicitly contrast itself with list_prompts.

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 a concrete downstream trigger: pass a topic to create_prompt / update_prompt to file a prompt under it. That tells the agent to call this first when it needs a topic reference. It stops short of explicit when-not conditions or naming sibling alternatives such as create_prompt_topic for the write side.

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

Deploy Server

Other Tools