Skip to main content
Glama
askads

Yandex Direct MCP

by askads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Удалить наборы быстрых ссылок

delete_sitelinks
Destructive

Deletes sitelink sets by ID, removing only those not linked to any ad. Use to clean up unattached sets.

Instructions

Удаляет наборы быстрых ссылок по id (удалить можно только наборы, не привязанные ни к одному объявлению).

Input Schema

NameRequiredDescriptionDefault
idsYesId наборов, которые нужно удалить.
client_loginNoЛогин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / client_login
      Added value: +{
+  "description": "Логин клиента агентства или кабинета в управлении (из list_clients). Если не указан — YANDEX_DIRECT_LOGIN из конфигурации, а без него собственный аккаунт токена.",
+  "pattern": "^[A-Za-z0-9][A-Za-z0-9._@-]{0,99}$",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / ids / description
      Previous value: -"Sitelink set ids to delete."New value: +"Id наборов, которые нужно удалить."
  3. First observedv0.1.0

TDQS

A4.2/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 known. The description adds valuable behavioral context beyond annotations by stating the unlinked-only restriction, which affects whether the call will succeed.

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?

The description is a single front-loaded sentence with no redundant restatement of the title. Every element, including the restriction, earns its place.

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 low-complexity destructive tool with full schema coverage and annotations, the description covers the essential precondition and identifier basis. It does not describe error behavior for linked sets, but the key constraint is present.

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%, and both parameters ('ids' and 'client_login') are documented in the schema. The description adds only that deletion is by ID, which is already evident from the schema, so baseline 3 is appropriate.

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 ('Удаляет наборы быстрых ссылок') and the identifier basis ('по id'). The parenthetical restriction further narrows the operation and distinguishes it from sibling tools like get_sitelinks and create_sitelinks_set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states a key precondition: only sitelink sets not linked to any ad can be deleted. This gives useful when-not guidance, though it does not explicitly point to get_sitelinks for discovering IDs or name alternatives.

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