Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

create_smart_view

Create an editable Smart View from keyword or page tags to group SEO data and open it in the SEOcrawl AI UI for analysis.

Instructions

Create a Smart View from a set of tags (read them from list_tags). type is keyword (over keyword tags) or page (over page tags). The view appears in the SEOcrawl AI UI exactly like a natively-created one and can be edited there.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a meaningful side effect: the created view 'appears in the SEOcrawl AI UI exactly like a natively-created one and can be edited there,' telling the agent the result is persistent and mutable. It omits permissions required, what happens on invalid tags, and whether creation is idempotent.

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?

Three short sentences, front-loaded with the action, then the input source, then the type constraint and post-creation behavior. No redundant restatement of the tool name and nothing that could be cut without losing 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 zero-declared-parameter creation tool with no annotations and no output schema, the description supplies the inputs, their source, the type enum, and the observable outcome. Missing only edge-case behavior such as permission requirements or failure modes, which keeps it just under a 5.

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 what actually informs the agent that this tool takes a set of tags plus a 'type' discriminator with keyword/page values. That is a substantial contribution beyond the schema, though the tag argument's format and cardinality are never specified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Create a Smart View from a set of tags') and names the two modes ('type is keyword ... or page'), which lets an agent distinguish this from sibling tools like list_smart_views and delete_smart_view. It does not explicitly contrast itself with create_tag or other creation tools, keeping it short of a 5.

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 prerequisite and route for obtaining inputs ('read them from list_tags') and explains the two valid type values, which is real when-to-use guidance. It stops short of saying when not to use this tool or how it relates to alternative view-creation paths.

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