Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

delete_crawler_project

Permanently deletes a crawler project, removing it from the app and read tools and stopping its weekly re-crawl; this action cannot be undone.

Instructions

Delete a Crawler project (write action, cannot be undone): it disappears from the app and from the read tools, and its weekly re-crawl stops.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present the description carries the full burden, and it does well: it declares the write nature, irreversibility, the two concrete consequences (removal from the app and from read tools, cessation of the weekly re-crawl). It does not address authorization requirements, whether historical crawl data is retained, or whether confirmation is needed for such a destructive 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?

A single front-loaded sentence with the verb and resource first, followed by a parenthetical that earns its place by disclosing the irreversible consequences. No filler.

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 consequence model is well covered for a destructive tool, but completeness falters on the two things an agent most needs before firing a delete: how the target is specified (no params at all) and what permissions or confirmation are required. No output schema exists, so return values are not the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero declared parameters, so no per-parameter semantics are needed and the baseline would be 4; however, for a delete operation the description never explains how the target project is identified, which is a meaningful omission given the schema is an empty object with additionalProperties true.

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 ("Delete a Crawler project") and immediately scopes it as a write action, which cleanly separates it from the create_/update_ crawler siblings without needing to name them.

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

Usage Guidelines3/5

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

Use is implied rather than stated: the "cannot be undone" warning signals this is a last-resort operation, but there is no explicit when-to-use guidance, no mention of an alternative (e.g., pausing re-crawls instead of deleting), and no prerequisites such as required permissions.

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