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

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Управление изображениями

manage_ad_images
Destructive

Upload Yandex.Direct ad images as base64, retrieve them with filters, or delete them by hash to keep ad creatives organized.

Instructions

Загрузить, получить или удалить изображения объявлений (AdImages). Для add данные передаются в base64.

Input Schema

NameRequiredDescriptionDefault
limitNoСколько объектов вернуть (максимум 10000)
actionYesЧто сделать: add, get или delete (необратимо)
imagesNoИзображения для загрузки; обязателен при action=add
offsetNoСмещение выборки: сюда передаётся LimitedBy предыдущей страницы
associatedNoФильтр при action=get: YES — только привязанные к объявлениям, NO — только свободные
ad_image_hashesNoХеши изображений: фильтр при action=get, обязателен при action=delete

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

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, and the description's mention of deleting is consistent with them. It adds the base64 payload requirement for add, but says nothing about permissions, batch limits (max 100 images), irreversibility of delete, or pagination behavior for get.

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?

Two short sentences, front-loaded with the action list, no filler. It is efficient but so terse that brevity comes at the cost of missing operational detail.

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?

A single tool multiplexing three actions with very different parameter requirements (images for add, hashes for delete, limit/offset/associated for get) and no output schema needs more than one line of prose. The description leaves the action-parameter mapping entirely to the schema, which is a real gap for a destructive multi-mode tool.

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 every parameter is already documented in detail. The only added statement — base64 for add — duplicates the schema's own 'Содержимое файла изображения в base64', so the description adds essentially nothing beyond structured data.

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?

Names three concrete verbs (upload, retrieve, delete) against a specific resource (AdImages), which matches the action enum exactly. It does not differentiate from any sibling, but no sibling in the list handles ad images, so the gap is minor.

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 on when to pick each action, no prerequisites, no mention that delete is irreversible or that get is paginated — all of which live only in the schema. The reader must infer action selection from the enum names alone.

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