Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

update_crawler_project

Rename a crawler project, switch its crawl mode, or replace its URL list; changes apply only to the next crawl.

Instructions

Rename a Crawler project, switch it between complete and list mode, or replace its URL list (write action). Nothing is crawled until you trigger the next crawl.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it declares this is a mutation, signals that the URL list is replaced rather than appended (an overwrite of existing data), and explicitly bounds the side effect by noting no crawl starts. It omits permissions, error/conflict behavior, and whether changes are reversible.

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 short sentences, zero filler, with the mutation scope front-loaded and the side-effect caveat second. Every clause carries information an agent needs.

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

Completeness3/5

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

The description covers what gets changed and the crawl side effect, which is the core need. But with no annotations, no output schema, and an empty parameter schema, it leaves notable gaps: how the target project is identified, required permissions, and what happens if the rename collides or the URL list is malformed.

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 input schema declares no properties at all, so the schema itself conveys nothing about argument names. The description compensates by naming the three modifiable concepts (project name, mode, URL list), though it does not specify argument names, formats, or how the target project is identified.

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 enumerates the exact three mutations: rename, mode switch (complete vs list), and URL-list replacement. Combined with siblings named create_/delete_crawler_project, an agent can immediately tell this is the in-place modifier of an existing project.

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?

Flagging '(write action)' and 'Nothing is crawled until you trigger the next crawl' gives the agent a clear sequencing rule: use this to change configuration, then use a separate crawl trigger. No explicit exclusions or named alternative tools are given, so it stops short of full when/when-not guidance.

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