Skip to main content
Glama
Sign In
keyso-mcp

keyso-mcp

by abukreev-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

keyso_get_report_simple_keyword_dashboard

Fetch a keyword dashboard with SEO metrics for a given search query and region, enabling competitor and domain analysis.

Instructions

Информация о ключевом слове (Дашборд) Method: GET Path: /report/simple/keyword_dashboard Пример запроса: https://api.keys.so/report/simple/keyword_dashboard?keyword=%D0%9F%D0%BB%D0%B0%D1%81%D1%82%D0%B8%D0%BA%D0%BE%D0%B2%D1%8B%D0%B5%20%D0%BE%D0%BA%D0%BD%D0%B0&base=msk

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": {
      "keyword": "<keyword>"
    },
    "name": "keyso_get_report_simple_keyword_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoin: query
tokenNoAPI token override (fallback: KEYSO_TOKEN env)
keywordYesin: query | Поисковый запрос
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?

There are no annotations, so the description must carry the behavioral burden. It discloses the HTTP method (GET) and an example request, suggesting a read-only operation, but it does not describe the response format, pagination, authorization requirements, rate limits, or any other runtime behavior.

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 purpose, followed by method/path and an example. There is no redundant prose, though it could add a sentence on expected output without becoming bloated.

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?

With 4 parameters, no annotations, and no output schema, the description is incomplete: it does not define the base parameter semantics, explain the dashboard fields, or give enough context to choose this over sibling tools. The example request is useful but only partial.

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 an example URL with keyword and base=msk, which helps illustrate usage, but it never explains what 'base' means or which values are valid, leaving that parameter semantically vague.

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 resource as 'keyword dashboard' and provides an explicit endpoint path, so an agent can tell it is a GET report about a single keyword. It is clear, but it does not explicitly differentiate this tool from the many other report/simple keyword tools, and it omits what metrics the dashboard contains.

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 dozens of sibling keyword-report tools such as organic_keywords, context_keywords, or similarkeys. The phrase 'keyword dashboard' implies a use case, but no exclusions or alternatives are provided.

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