Skip to main content
Glama
Sign In
keyso-mcp

keyso-mcp

by abukreev-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

keyso_post_monitoring_id_link_words

Update the target URL for a phrase or group of phrases in position monitoring. Specify the monitoring ID and new URL to refresh tracking.

Instructions

Мониторинг позиций - обновление целевого URL у фразы или группы фраз. Method: POST Path: /monitoring//link-words Пример запроса https://api.keys.so/monitoring/<id>/link-words

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>",
      "body": "<body>"
    },
    "name": "keyso_post_monitoring_id_link_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesin: path (auto-detected)
bodyYesJSON 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 reveals only that the operation updates a URL, but not side effects, required permissions, whether the update replaces all matches, or what a successful response looks like.

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 brief and front-loaded with the main purpose, followed by method, path, and an example URL. There is little waste, though the Russian sentence could be slightly more structured for an API agent.

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 tool with an opaque required body and no output schema or annotations, the description is insufficient. An agent cannot construct the request body or predict response behavior from the information provided.

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 reported as 100%, so the baseline is 3, but the body parameter is a generic 'JSON body' object with empty properties. The description adds narrative context about target URL and phrase/group, but it does not specify the actual body fields or format needed to invoke the tool correctly.

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 and resource: 'обновление целевого URL у фразы или группы фраз' (updating the target URL for a phrase or group of phrases) and gives the POST path. This distinguishes it from sibling monitoring tools, though it could be more explicit about what 'link-words' means in this context.

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 on when to use this tool versus alternative monitoring tools, nor any exclusions or prerequisites. The description gives the endpoint but does not explain how this update operation fits among the many sibling tools like patch_monitoring_id or post_monitoring_id_start.

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