Skip to main content
Glama
Sign In
keyso-mcp

keyso-mcp

by abukreev-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

keyso_delete_clustering_uid

Delete a clustering report by its unique identifier to remove it from Keys.so SEO data.

Instructions

Кластеризация - удаление проекта Method: DELETE Path: /clustering/ Пример запроса https://api.keys.so/clustering/b8095aa8g82defb29f9a1660640fa7f9

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_delete_clustering_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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does disclose that this is a DELETE operation and that it removes a clustering project, but it does not state whether deletion is permanent, what consequences it has, whether special permissions are needed, or what the response looks like.

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 front-loaded with the core intent, followed by method, path, and an example. No unnecessary filler is present, though the 'Кластеризация - удаление проекта' line is more of a title than a full explanatory sentence.

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 delete operation with one required parameter, the description gives enough to make the request. However, with no annotations and no output schema, it omits response/status information and any note about irreversibility or authorization, and it slightly conflates 'project' with 'report'.

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%, so the uid parameter is already documented as a path parameter. The description adds a concrete path template and example URL, which helps clarify the uid placement, but it does not add meaningful semantics for token or base_url beyond what the schema already provides.

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 clearly states the operation is deleting a clustering project and provides the HTTP method and path. It is specific enough to distinguish from the clustering creation/list/get siblings, though it does not explicitly name any sibling alternatives.

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 description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The delete intent is implied by the wording, but the description does not explain the conditions or context for using it.

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