Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

trigger_site_audit_crawl

Start a fresh site crawl to queue pages for SEO auditing and return an audit ID with status and pages queued. Use it before read tools to analyze completed crawl results.

Instructions

Start a fresh crawl (write action) — queues the crawl and spends the project's crawler credits (separate from MCP credits) in proportion to the pages crawled. Supports complete and list modes; returns audit_id, status, started_at and pages_queued. Results become available to the read tools once the crawl finishes.

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

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 supplied, the description carries the full behavioral load and does it well: it discloses that this is a write/queue operation, that it consumes project crawler credits (distinct from MCP credits) proportionally to pages crawled, and that results are asynchronous. It does not cover permissions, failure behavior, or whether re-triggering supersedes an in-flight crawl, so a 4 rather than 5.

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?

It is a single dense paragraph that front-loads the action and its write/cost implications before the return fields and post-conditions. Every sentence carries information, though the credit-cost clause is slightly convoluted and could be split for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the definition covers the important ground: write semantics, cost model, accepted modes, exact return fields (audit_id, status, started_at, pages_queued), and the post-condition that reads become valid only after the crawl completes.

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?

There are zero declared parameters, so the baseline is 4. The description does mention 'complete and list modes', which hints at an optional mode property tolerated by additionalProperties, but it never says how that mode is supplied, leaving the agent to guess at the wire format.

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 pairs a specific verb with its resource ("Start a fresh crawl") and immediately marks it as a write action. It also distinguishes it from the read siblings by noting that results only become available to the read tools once the crawl finishes, so an agent can separate trigger_site_audit_crawl from list_site_audit_issues or compare_site_audit_crawls without inspecting other schemas.

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 context for when to call it: you want a fresh crawl, you accept spending crawler credits, and you understand reads must wait until completion. What it lacks is an explicit negative case or prerequisite (for example, what to do if a crawl is already running, or how this differs from create_crawler_project).

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