Skip to main content
Glama
Sign In
keyso-mcp

keyso-mcp

by abukreev-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

keyso_get_clustering_node_uid

Retrieve clustering folders for a given report UID to analyze keyword grouping and SEO structure via the Keys.so API.

Instructions

Получение папок кластеризации Method: GET Path: /clustering/node/ Пример запроса https://api.keys.so/clustering/node/59f2bо9004be5449891467f07a4eb5a9

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uid": "<uid>"
    },
    "name": "keyso_get_clustering_node_uid"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYesin: path | Идентификатор отчёта
tokenNoAPI token override (fallback: KEYSO_TOKEN env)
base_urlNoOverride API base URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

There are no annotations, so the description carries the behavioral burden. It explicitly declares 'Method: GET' and uses 'Получение' (retrieval), which signals a read-only operation, and gives an example request. However, it does not mention auth requirements, response format, error behavior, or rate limits.

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?

The description is short and well-structured: purpose comes first, followed by method, path, and example. Every line earns its place, with no unnecessary filler.

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 simple GET with one required parameter, the description gives the essential endpoint mechanics: method, path, and example. However, there is no output schema and no description of what the returned 'folders' data looks like, nor any guidance on when this endpoint should be preferred over related clustering tools.

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 description coverage is 100%, and the schema already explains uid, token, and base_url. The description adds a URL template and a concrete example for uid, which helps confirm how the path parameter is used, but it does not add significant meaning beyond the schema.

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 action ('Получение' — retrieving) and resource ('папок кластеризации' — clustering folders), and gives the API path. It is clear, but it does not explicitly differentiate this from the very similar sibling keyso_get_clustering_node_uid_id_keywords.

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?

No usage guidance is provided: there is no statement of when to use this tool versus alternatives, no exclusions, and no context about which workflow requires it. The sibling list contains many similar clustering endpoints, so an agent gets no selection criteria from the description.

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