keyso-mcp

keyso_delete_ai_tracker_id

Remove an AI tracker project from Keys.so by its ID to clean up unused trackers and keep SEO monitoring data organized. Deletes the specified tracker permanently.

Instructions

Трекер ИИ - удаление проекта Method: DELETE Path: /ai_tracker/ Пример запроса https://api.keys.so/ai_tracker/<id>

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": {
      "id": "<id>"
    },
    "name": "keyso_delete_ai_tracker_id"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	in: path (auto-detected)
`token`	No	API token override (fallback: KEYSO_TOKEN env)
`base_url`	No	Override API base URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 20, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It discloses the HTTP method (DELETE) and path, which imply destruction, but it does not state whether deletion is permanent, whether it cascades to associated data (prompts, competitors), or what authentication is required. This leaves significant behavioral ambiguity for a destructive operation.

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?

Three lines: a clear Russian label, method+path, and an example request. All information is relevant and front-loaded; no fluff or redundant explanation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description omits essential context: irreversibility, cascade effects, permission requirements, or what response to expect. The typical agent needs more than a path to safely invoke a delete operation.

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 baseline is 3. The description's example URL with <id> adds minimal meaning beyond the schema, though it does reinforce that id is a path parameter. It does not explicitly explain that id is the AI tracker project ID, but the title provides that context.

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 states a specific verb (delete) and resource (AI tracker project) in Russian ('удаление проекта' = delete project) plus the HTTP method and path. This clearly differentiates from sibling tools like keyso_delete_ai_tracker_id_prompts or keyso_delete_ai_tracker_id_competitors, which delete sub-resources rather than the project itself.

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 guidance is given on when to use this tool versus alternatives. There is no mention of alternatives or exclusions; an agent must infer from the name and sibling list that this handles project-level deletion only.

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

Deploy Server