Skip to main content
Glama
Pavelsiba

yandex-direct-mcp-plus

by Pavelsiba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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

manage_ad_images
Destructive

Upload, list, or delete Yandex.Direct ad images: pass base64 data to add, filter by association to get, or use hashes to delete.

Instructions

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

Input Schema

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

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

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so safety expectations are covered structurally. The description adds only that add operations carry base64 data, but does not disclose that delete is irreversible, what dry_run does behaviorally, or other operational traits beyond what annotations and schema already provide.

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 compact sentence that front-loads the core operations before the add-specific detail. There is no wasted wording or redundant preamble.

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?

Given the rich schema coverage and destructive/open-world annotations, the description is minimally adequate: it identifies the actions and notes the base64 requirement for add. However, it provides no usage guidance, no return-value context for get, and no behavioral notes on delete irreversibility or dry_run.

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 the input schema already documents all 7 parameters, including action, images, filters, dry_run, and pagination. The description repeats that add data is base64, which the schema also states, adding no extra semantic meaning.

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 specific verbs (load, retrieve, delete) and a specific resource (ad images / AdImages), so an agent can distinguish it from sibling tools such as manage_ads or manage_campaigns. It covers all three action modes in the tool name and schema.

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?

The description does not say when to prefer this tool over alternatives like manage_ads or list_ads, nor does it state when not to use it. It only notes that add requires base64 data, which is an operational detail rather than usage guidance.

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