Skip to main content
Glama

Black SEO Analyzer

start_crawl

Queue a crawl of a whole site and return a job_id immediately; a worker runs the crawl and the pages count against the account's rolling 30-day page budget. Use it only when the user asks to crawl or audit a site, or names a number of pages; a request to check a single URL, even a homepage, is check_page, and never start a crawl alongside check_page unasked. Pass the max_pages the user named. One crawl per account runs at a time. Poll crawl_status with the job_id until state is "finished", then read the results with issues_summary and query_issues. max_pages defaults to 500 and is capped at 2000 and at the pages remaining in the budget. JavaScript rendering (spa) is not available on the hosted connector.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "start_crawl"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaNoRender JavaScript with a headless browser. Much slower; use only for single-page apps.
urlYesAbsolute URL to start crawling from, including the scheme.
max_pagesNoMaximum number of pages to fetch. Defaults to 500. Raise it only when the user has asked for a full-site audit and accepts a longer run.
audit_profileNoWhich analyzers to run: "full" (default), "standard", "core", "critical", or "quick". Use "quick" or "critical" when the user wants a fast answer rather than a complete audit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations by disclosing the asynchronous worker model, that pages count against a rolling 30-day budget, that only one crawl per account runs at a time, that max_pages defaults to 500 and is capped at 2000 and by remaining budget, and that spa rendering is unavailable on the hosted connector. These are the operational facts an agent needs before committing an expensive, non-idempotent call.

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?

Dense but front-loaded: purpose and async nature first, then routing rule, then parameter guidance, then follow-up workflow, then limits. Every sentence carries actionable information, with no filler or repetition.

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 non-idempotent, budget-consuming async job with no output schema, the description supplies the cost model, concurrency limit, parameter ceilings, the polling contract, and the follow-up tools. Nothing an agent needs in order to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the cap of 2000, the budget-derived ceiling, and the instruction to pass only the page count the user named. It does not explain audit_profile values, though the schema already does that.

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 ("Queue a crawl of a whole site") plus the immediate return value ("return a job_id"). It explicitly distinguishes itself from the sibling check_page, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Gives positive triggers (user asks to crawl/audit a site or names a page count), an explicit exclusion ("a request to check a single URL, even a homepage, is check_page"), and a prohibition against running both unasked. It also names the downstream sequence: poll crawl_status until finished, then issues_summary and query_issues.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.