keyso-mcp

keyso_delete_serp_id

Delete a SERP parsing project by its ID from the Keys.so API to remove unwanted search engine results data.

Instructions

Онлайн парсер выдачи - удаление проекта Method: DELETE Path: /serp/ Пример запроса https://api.keys.so/serp/<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_serp_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.4/5.0

Behavior3/5

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

With no annotations, the description carries the burden of conveying the destructive behavior, and it does by saying 'deletion of a project' and specifying Method: DELETE. It does not, however, state whether deletion is permanent, whether associated SERP data is removed, what authorization is needed, or what response is returned.

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 concise and front-loaded: it states the purpose first, then the method and path, then an example request. The example URL repeats the path, but this redundancy is minor and helps make the endpoint immediately actionable.

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 and no output schema, the method, path, and target resource are enough to understand the core call. It is incomplete, though, because it does not mention response/error behavior, authorization requirements, or any effect beyond deleting the project.

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 baseline is 3. The description adds the path template /serp/<id>, confirming that the id parameter identifies the resource in the URL, but it does not add meaningful semantics beyond what the input 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 this tool deletes a project ('удаление проекта') and specifies the HTTP method DELETE and path /serp/<id>, so an agent can identify the target resource. It is not a 5 because it does not explicitly distinguish this SERP-project deletion from sibling delete tools such as keyso_delete_wordstat_delete_project or keyso_post_projects_delete, though the path helps disambiguate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use is implied: call this tool when you need to delete a specific SERP/project by its id. However, there is no explicit when/when-not guidance, no mention of alternatives, and no cautionary context about destructive consequences for a tool with many sibling delete operations.

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

Deploy Server