Skip to main content
Glama
Sign In
keyso-mcp

keyso-mcp

by abukreev-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

keyso_post_ai_tracker_id_start

Trigger an update for an AI tracker by providing its ID. Starts the refresh process to gather current SEO data for the specified tracker.

Instructions

Трекер ИИ - запуск обновления Method: POST Path: /ai_tracker//start Пример запроса https://api.keys.so/ai_tracker/<id>/start

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

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 provided, so the description carries the full burden of behavioral disclosure. It only states that a POST update is started; it does not disclose side effects, whether the operation is asynchronous, whether repeated calls are safe, or how to check the resulting state.

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 very short and front-loaded, giving the action, HTTP method, path, and a concrete example request. It contains minimal waste, though the example URL partly duplicates the path already shown.

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-style endpoint with no annotations and no output schema, this description is thin. It does not explain what happens after the update is started, whether the update runs asynchronously, or how to poll for completion. An agent can construct the request but cannot fully anticipate the tool's behavior.

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 schema already documents the parameters. The description adds an example URL but no additional meaning for `id`, `body`, `token`, or `base_url`. This meets the baseline for a fully schema-covered tool but does not go beyond it.

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 opens with 'AI Tracker - start update', a concrete verb-resource pair indicating this tool triggers an update for an AI tracker identified by an id. The endpoint path `/ai_tracker/<id>/start` reinforces the action. It does not explicitly differentiate from sibling tools, but the name and path make the operation reasonably distinguishable from create/delete/report endpoints.

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 about when to use this tool versus alternatives, when not to use it, or what prerequisites must be met. The phrase 'start update' implies a triggering use case, but there is no mention of related status-checking endpoints or conditions under which this should be called.

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