Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_smart_views

Retrieve keyword and page Smart Views for a property, including view ID, name, type, and grouped tag names, to inspect tag-based SEO organization.

Instructions

List the keyword and page Smart Views defined for a property — each with view_id, name, type (keyword | page) and the tag names it groups. Per-tag member counts come from list_tags.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4/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 behavioral burden. It discloses the response shape and notes that tag member counts come from a separate tool, which is useful, but it does not state read-only safety, pagination behavior, authorization needs, or how the target property is determined.

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?

It is a single front-loaded sentence with no filler. The returned fields and the list_tags cross-reference are packed in cleanly.

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 list with no output schema, the description does a good job of explaining the return values and the related list_tags dependency. The remaining gap is that it does not clarify how the property context is established despite saying views are 'defined for a property.'

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 has zero parameters, so the schema baseline is 4. The description adds useful meaning by explaining what the returned view records contain, even though there are no input parameters to document.

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 uses a specific verb and resource: 'List the keyword and page Smart Views defined for a property.' It also states the returned fields (view_id, name, type, tag names), so an agent can distinguish this from list_tags and the create/delete smart view tools.

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?

Usage is mostly implied by the listing purpose. The description gives one helpful boundary: per-tag member counts come from list_tags, not this tool. It does not explicitly say when to choose this over create_smart_view or delete_smart_view, nor does it clarify whether property scoping is implicit.

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