Skip to main content
Glama
Sign In

Seonix

by io.github.pahaa97
OverviewDiscussionsAdmin

Keyword clusters

list_clusters
Read-onlyIdempotent

Topic clusters (one target page each) with primary keyword, intent, page type, priority, volume, Search Console impressions and winnability. The content plan is built from these.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (default 20, max 100).
offsetNoSkip this many clusters.
statusNodraft | approved | brief_ready | content_created.
project_idNoProject id or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world behavior, so the safety profile is covered. The description adds useful domain context — that each cluster maps to exactly one target page and carries intent/priority/winnability — but says nothing about pagination behavior, ordering, or what happens when the project has no clusters.

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?

Two short sentences with no filler, and the field inventory is front-loaded. It could be improved by leading with the action verb, but nothing here is wasted.

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?

For a read-only, four-parameter listing tool with full schema coverage and no output schema, the description is adequate but thin: it sketches returned fields while omitting pagination semantics, ordering, and the relationship to get_cluster. An agent could call it correctly but not confidently.

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?

Schema coverage is 100%, with limit/offset/status/project_id each documented in-schema, so the baseline of 3 applies. The description adds nothing about parameters — it does not explain the status lifecycle values or how project_id interacts with the listing scope.

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

Purpose3/5

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

The description names the resource (topic clusters) and enumerates the fields returned, which tells an agent what data is behind the tool. But it never states the action — 'List' only appears in the tool name — and it does not distinguish this collection endpoint from the sibling get_cluster that retrieves a single cluster. Purpose is inferable rather than stated.

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?

The only usage signal is 'The content plan is built from these,' which hints at downstream relevance but gives no when-to-call condition. There is no mention of alternatives such as get_cluster for a single item or list_keyword_candidates for pre-cluster keywords, and no prerequisite or filtering guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Seonix toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources