Skip to main content
Glama
yandex-direct-mcp-plus

yandex-direct-mcp-plus

by Pavelsiba

Удалить быстрые ссылки

delete_sitelinks
Destructive

Deletes quick link sets by ID for Yandex.Direct; if a set is attached to an ad, deletion is blocked until the link is removed first.

Instructions

Удалить наборы быстрых ссылок по 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": {
      "sitelink_set_ids": "<sitelink_set_ids>"
    },
    "name": "delete_sitelinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
sitelink_set_idsYesНаборы, которые нужно удалить; ID берутся из list_sitelinks

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / dry_run
      Removed value: -{
      -  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
      -  "type": "boolean"
      -}
  2. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
      +  "type": "boolean"
      +}
  3. First observedv1.6.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is visible. The description adds useful platform-specific behavior: a sitelink set attached to an ad cannot be deleted. It still does not describe atomicity, partial failure handling, or whether the deletion is permanent beyond the annotation's destructive hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the action and blocking condition front-loaded. There is no filler, repetition, or unnecessary detail.

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 destructive batch-delete operation, annotations cover the destructive nature, and the schema fully documents the input. However, the description omits operational outcome details such as whether deletion is atomic or how partial failures are reported, leaving a meaningful gap for an agent invoking this at scale.

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 coverage is 100% for the single array parameter, including item pattern, min/max items, and a note that IDs come from list_sitelinks. The description only restates that deletion is by ID and adds no further syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb ('Удалить') and resource ('наборы быстрых ссылок') with the scope 'по ID'. It distinguishes deletion from siblings like list_sitelinks and set_sitelinks by the verb, though it does not explicitly name those alternatives.

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?

Implies use when the agent knows set IDs and needs to remove them, and adds the important constraint that ad-linked sets cannot be deleted. It does not explicitly say when to prefer another tool, and the instruction to obtain IDs from list_sitelinks appears only in the schema, not the description.

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