Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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

delete_sitelinks
Destructive

Deletes sitelink sets by ID in Yandex.Direct. Fails if a set is attached to an ad; supports dry_run for preview.

Instructions

Удалить наборы быстрых ссылок по ID. Набор, привязанный к объявлению, Директ удалить не даст.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNotrue — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.
sitelink_set_idsYesНаборы, которые нужно удалить; ID берутся из list_sitelinks

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "true — ничего не менять: проверить параметры и вернуть тела запросов, которые ушли бы в Директ. Чтение при этом выполняется.",
+  "type": "boolean"
+}
  2. First observedv1.6.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds a non-obvious behavioral constraint beyond the annotations: deletion fails if the set is attached to an ad. It doesn't describe the return shape, but that is acceptable for a delete tool with no output schema.

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 tight sentences with the action stated first and the key caveat second. No filler, nothing wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive delete with no output schema, the description covers the operation and the main failure condition, and annotations cover the risk profile. It could go further by pointing to list_sitelinks for ID discovery, which the schema mentions but the description itself omits.

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 both parameters (sitelink_set_ids and dry_run, including a 1–1000 item bound) are fully documented in the schema. The description only echoes 'by ID' and adds no syntax or format detail beyond what the schema already provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource (delete sitelink sets by ID), which unambiguously distinguishes it from its siblings list_sitelinks and set_sitelinks. An agent can immediately tell this is the removal operation for sitelink sets.

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?

It provides an important exclusion — Direct won't allow deleting a set that is bound to an ad — which is genuine usage guidance. However, it never names alternatives (e.g. unlink via update, or use list_sitelinks first to find IDs) nor explicitly states the when-to-use condition, so guidance is implied rather than complete.

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