Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

create_crawler_project

Create a site crawler project from Search Console, sitemaps, or custom URLs to set up weekly re-crawls; starting it requires a separate trigger and uses no credits at creation.

Instructions

Create a Crawler project (write action): crawl the whole site, discovered from Search Console and sitemaps, or a fixed list of your own URLs. Creating it crawls nothing and spends no credits; start it with trigger_site_audit_crawl, and it re-crawls weekly after that.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.6/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 declares this is a write action, states there is no crawl and no credit spend at creation time, and discloses the ongoing effect that the project re-crawls weekly. It falls short of stating permission/authorization requirements or what happens if a project already exists for the site, which matters for a mutating tool with a recurring side effect.

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 compact sentences, zero filler, and the most decision-relevant fact (creation does not crawl or spend credits) is front-loaded ahead of the follow-up action and the recurring-schedule note.

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 creation tool with no annotations and no output schema, the definition covers cost, side effects, and the required follow-up call. It leaves a small gap in not saying what the call returns (e.g., an identifier needed to pass to 'trigger_site_audit_crawl') or how to choose the crawl source given there are 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 takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema shows; baseline 4 applies. The mention of Search Console/sitemap discovery versus a fixed URL list is conceptual context rather than parameter mapping, and it is unclear how those options are supplied given the schema exposes no fields.

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 opens with a specific verb and resource ('Create a Crawler project') and immediately disambiguates it from the crawl action itself ('Creating it crawls nothing'). It also names the two configurable crawl scopes, so an agent knows exactly what is being created versus what a sibling tool does.

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?

Explicitly routes the agent: creating the project does not crawl, and the crawl must be started with 'trigger_site_audit_crawl'. The condition that selects the sibling (you want an actual crawl) is stated directly, and the weekly re-crawl behaviour tells the agent it does not need to re-create the project later.

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