Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

delete_smart_view

Permanently deletes a saved Smart View by view_id, removing it from the SEOcrawl AI UI while leaving underlying tags intact; applied-filter IDs return not_found.

Instructions

Delete a Smart View by its view_id. Permanent and removes the view from the SEOcrawl AI UI too; the underlying tags are not affected. A regular applied-filter id returns not_found.

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

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 disclosure burden and does so well: it states the deletion is permanent, that the view disappears from the SEOcrawl AI UI, that the underlying tags are unaffected, and what error a wrong id type produces. It omits permission requirements or any confirmation/reversibility nuance, which is the remaining gap for an irreversible mutation.

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 with the destruction semantics front-loaded and nothing redundant. Every clause (permanence, UI removal, tags preserved, error case) adds distinct information.

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 permanent mutation with no annotations, no output schema, and a schema that documents nothing, the description covers what gets destroyed, side effects, and one failure mode — enough to invoke it correctly. Only authorization requirements and confirmation expectations are 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?

The input schema declares no properties, so the description is the only source of parameter meaning and it names view_id plus the important distinction that this must be a Smart View id, not an applied-filter id. It stops short of stating the id's format or where to obtain it, so it is informative but not exhaustive.

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 names a specific verb and resource ("Delete a Smart View") and identifies the keying identifier ("by its view_id"), which clearly separates it from siblings like create_smart_view and list_smart_views. The agent can tell it is the destructive counterpart to the create/list tools 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 Guidelines4/5

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

It gives a concrete negative condition — passing a regular applied-filter id yields not_found — which tells the agent when this call will fail rather than silently misbehave. It does not explicitly name an alternative tool for that mistaken case, so it falls short of full when/when-not routing 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