Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

create_prompt_topic

Create or fetch a prompt topic by title as an idempotent upsert, so reusing a title returns the existing topic for grouping prompts.

Instructions

Create (or fetch) a prompt topic by title — an idempotent upsert, so re-creating an existing title returns it unchanged with created=false. Topics group prompts on the Prompt Tracking page.

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": "create_prompt_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses idempotency, the unchanged-return behavior on collision, and the created=false flag in the response. It omits authentication requirements and error conditions, but the core mutation semantics are unusually well disclosed.

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, front-loaded with the verb and idempotency guarantee. Every clause adds information: the upsert behavior, the collision return value, and the domain context of what topics group.

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, no-output-schema tool, the description covers purpose, idempotency, and the return signal well enough to call it correctly. The main residual gap is that the title argument is described but not reflected anywhere in the schema, leaving ambiguity about how to supply it.

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 schema declares zero parameters, yet the description reveals that the operation is keyed "by title", which is the essential input meaning an agent needs. It also explains the meaning of the created flag on return, compensating for the empty schema; only the exact parameter naming/format remains unstated.

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?

The description gives a specific verb and resource ("Create (or fetch) a prompt topic") and clarifies the semantics as an idempotent upsert keyed by title. It distinguishes itself semantically from update_prompt_topic by stating that re-creating an existing title returns it unchanged, though it doesn't name siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical "(or fetch)" implies this can substitute for a read when you know the title, which is a useful hint. However, there is no explicit when-not guidance, no statement about when to prefer list_prompt_topics, and no prerequisites such as required permissions.

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