Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_keyword_clusters

Retrieve Search Console keywords grouped into topic clusters, with clicks, impressions, average position, Google Ads search volume, traffic value, and a 12-month demand curve.

Instructions

Your Search Console keywords grouped into topic clusters (built in the Keyword Map), each with clicks, impressions, average position, Google Ads search volume, traffic value and its 12-month demand curve.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the shape of the returned data well (clicks, impressions, average position, Ads search volume, traffic value, 12-month demand curve), which is real value. However, it says nothing about scope (which site/property the clusters come from, especially given zero input parameters), pagination, or limits on result size.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the resource statement front-loaded and no filler. The trailing field enumeration is long but every item describes a distinct returned metric, so it earns its place.

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?

With no output schema, the description usefully enumerates return fields, which covers the biggest gap. It remains incomplete for a zero-parameter tool where the implicit scope (which connected property/site the clusters belong to) and any result limits or ordering are unexplained.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description sensibly spends its words on output content instead.

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 names a specific resource (Search Console keywords grouped into topic clusters built in the Keyword Map), so an agent can tell what data this returns. It is clear about content but never uses an explicit verb like 'list' or 'retrieve', relying on the tool name for that; it also does not distinguish itself from siblings such as get_keyword_detail or find_keyword_opportunities.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives. With siblings like get_keyword_detail (single keyword) and list_keywords_for_page (per-page keywords) present, an agent gets no signal about when cluster-level aggregation is the right choice.

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