Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

trigger_prompt_run

Runs a tracked prompt immediately on every tracked AI engine instead of waiting for its schedule, with answers appearing in list_prompt_runs within minutes.

Instructions

Run a tracked prompt now on every engine it tracks instead of waiting for its schedule (write action). The answers land in list_prompt_runs within a few minutes; one on-demand run per prompt per hour, shared with the app's Run now.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it flags this as a write action, discloses the per-prompt hourly rate limit shared with the app's Run now, and explains the asynchronous result path ('answers land in list_prompt_runs within a few minutes'). It does not cover permission requirements or what happens when the rate limit is hit.

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 dense sentences with zero waste. The action and scope are front-loaded, followed by the operational constraints and result destination, in a logical order.

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 param-less write tool with no output schema, the description covers the key invocation facts: mutation semantics, rate limiting, latency, and where results appear. The main remaining gap is that it never explains how 'a tracked prompt' is selected when the tool accepts no parameters.

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 has zero parameters, so the baseline is 4 and the description is not expected to explain parameter syntax. It could clarify how the target prompt is identified given the absence of an ID parameter, but the schema itself exposes no parameters to document.

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?

The description states a specific verb and resource ('Run a tracked prompt now') plus scope ('on every engine it tracks'), and explicitly contrasts it with waiting for the schedule. An agent can distinguish it from list_prompt_runs and the create/update prompt 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?

It gives clear when-to-use context: trigger immediately instead of waiting for the scheduled run. The rate-limit sentence adds a practical constraint ('one on-demand run per prompt per hour, shared with the app's Run now'), though it does not name an alternative tool or state explicit when-not conditions beyond the hourly cap.

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