Skip to main content
Glama
Sign In
keyso-mcp

keyso-mcp

by abukreev-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

keyso_delete_ai_tracker_id_prompts

Delete AI tracker prompts by providing the tracker ID. Removes all associated prompt data from the specified tracker in the Keys.so API.

Instructions

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

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

Input Schema

NameRequiredDescriptionDefault
idYesin: path (auto-detected)
bodyNoJSON body
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 present, so the description carries the full burden of behavioral disclosure. It identifies a DELETE operation but does not state that deletion is permanent, what scope of data is removed, whether authentication is required, or how related data is affected. This is minimal rather than misleading.

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 leads with the core purpose, method, and path. The example request is useful and the text avoids unnecessary filler, though it could include a bit more explanatory context without becoming verbose.

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 destructive tool with no annotations and no output schema, the description lacks important context such as success/error behavior, return value, whether all prompts are deleted, and any warning about irreversibility. The example URL helps, but the description is not complete enough for an agent to fully anticipate the outcome.

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%, so the parameters are already documented. The description adds a concrete URL example showing the id in the path, but it does not meaningfully enrich the meaning of the id, body, token, or base_url parameters 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 states the action ('удаление промптов' — deleting prompts) and the resource (AI tracker prompts), along with the HTTP method and path, so an agent can understand what the tool does. It does not explicitly differentiate from sibling tools like delete_ai_tracker_id_prompts_group, but the path and noun are specific enough to avoid major confusion.

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 guidance about when to use this tool versus the POST prompts, delete prompt group, or delete tracker siblings. The description only provides method/path facts and an example URL, leaving the agent to infer the appropriate context from the tool name.

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