Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

create_prompt

Create a tracked AI prompt to monitor questions across ChatGPT, Claude, Gemini, Perplexity, and Google AI modes. Set country, language, cadence, and topic; the first run is queued.

Instructions

Create a tracked prompt: the question that runs against the AI engines. Set the engine list (chatgpt, claude, gemini, perplexity, ai_overview, ai_mode), country, response language and cadence (daily, week or month), and optionally file it under a topic by topicId or topicTitle (find-or-create). The first run is queued at once.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full load — and it discloses two real side effects: the first run is queued at once, and topic resolution is find-or-create. It leaves auth or permission requirements and the response shape unstated.

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 sentences, front-loaded with the resource definition and followed by configuration and side-effect information; nothing is filler. The inline enum listing is dense but justified given the empty schema.

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?

With no annotations, no output schema, and an unspecified schema, the description still tells an agent what it must supply and what happens immediately after the call. It stops short of saying what identifier or object comes back, which matters for chaining into get_prompt_detail or trigger_prompt_run.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is an empty object with additionalProperties true, so the description is the only parameter documentation an agent gets. It enumerates the valid engine values, names country, response language and cadence with its enum-like values (daily, week, month), and explains the topicId/topicTitle find-or-create behavior.

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 and then defines it: 'Create a tracked prompt: the question that runs against the AI engines.' It also disambiguates from create_prompt_topic by noting that topic filing is an optional find-or-create side effect rather than the operation itself.

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 description implies when to use it by listing the configuration a new prompt requires, and it tells the agent that a run is queued immediately. It never states when to use update_prompt or trigger_prompt_run instead, and it never says whether engine list, cadence, or country are mandatory.

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