Skip to main content
Glama
Sign In
keyso-mcp

keyso-mcp

by abukreev-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

keyso_post_wordstat_create_project

Create a new Wordstat parsing project to gather Yandex keyword search volume data. Submit the task via API and start collecting SEO metrics for keyword analysis.

Instructions

Онлайн парсер Wordstat - создание задания Method: POST Path: /wordstat/create-project Пример запроса: https://api.keys.so/wordstat/create-project

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keyso_post_wordstat_create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It only reveals HTTP method, path, and that it creates something; it does not mention auth needs, asynchronous behavior, response format, or side effects.

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 compact and front-loaded, with the purpose stated first and the method/path plus a request example following. There is no filler, though the missing body specification limits practical value.

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?

The tool lacks annotations and an output schema, and the description does not specify the request body shape, response behavior, or follow-up steps such as polling status via sibling wordstat tools. An agent can find the endpoint but cannot reliably construct a valid request.

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% because token, base_url, and body all have at least a description, so the baseline is 3. The description adds no parameter details, and the body schema is just 'JSON body' with no properties, leaving the actual create-project payload undocumented.

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 a specific action ('создание задания' — creating a task) for the Wordstat parser and provides the endpoint method/path. This helps distinguish it from the many sibling wordstat tools that update, delete, or fetch status.

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 by the create wording and the `/wordstat/create-project` path, but the description does not explicitly state when to prefer it over alternatives or mention any prerequisites such as authentication or existing project requirements.

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