Skip to main content
Glama
askads

Yandex Direct MCP

by askads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Создать текстовое объявление

create_text_ad

Creates a draft text ad in a Yandex Direct ad group using a title, text, and landing page URL, enabling API-based ad creation.

Instructions

Создаёт текстовое объявление (TextAd) в группе объявлений. Новые объявления создаются черновиками. TextAdAdd требует хотя бы одно из Href/TurboPageId/BusinessId — этот инструмент передаёт посадочную страницу через href (обязателен); объявление с BusinessId вместо ссылки создаётся через raw_request. Визитки (VCardId) Директ больше не поддерживает: контакты задаются организацией из Яндекс Бизнеса (BusinessId). Директ создаёт такие объявления комбинаторными (тип RESPONSIVE_AD), а Title2 объединяет с Title через «. », если вместе они короче 56 символов, иначе отбрасывает; о таких изменениях API сообщает предупреждениями.

Input Schema

NameRequiredDescriptionDefault
hrefYesURL посадочной страницы (обязателен для TextAdAdd).
textYesТекст объявления, до 81 символа.
titleYesЗаголовок (Title 1), до 56 символов.
mobileNoМобильное ли это объявление. Поле в API устарело (значение принудительно NO), но остаётся обязательным.
title2NoВторой заголовок (Title 2), до 30 символов.
adGroupIdYesId родительской группы объявлений.
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. Changed9 schema fields changedv1.5.1
    • changedInput schema / properties / adGroupId / description
      Previous value: -"Parent ad group id."New value: +"Id родительской группы объявлений."
    • changedInput schema / properties / href / description
      Previous value: -"Landing page URL."New value: +"URL посадочной страницы (обязателен для TextAdAdd)."
    • addedInput schema / properties / href / minLength
      Added value: +1
    • addedInput schema / properties / mobile / default
      Added value: +false
    • changedInput schema / properties / mobile / description
      Previous value: -"Whether this is a mobile ad."New value: +"Мобильное ли это объявление. Поле в API устарело (значение принудительно NO), но остаётся обязательным."
    • changedInput schema / properties / text / description
      Previous value: -"Ad body text, up to 81 characters."New value: +"Текст объявления, до 81 символа."
    • changedInput schema / properties / title / description
      Previous value: -"Title (Title 1), up to 56 characters."New value: +"Заголовок (Title 1), до 56 символов."
    • changedInput schema / properties / title2 / description
      Previous value: -"Second title (Title 2), up to 30 characters."New value: +"Второй заголовок (Title 2), до 30 символов."
    • changedInput schema / required
      Previous value: -[
-  "adGroupId",
-  "title",
-  "text"
-]New value: +[
+  "adGroupId",
+  "title",
+  "text",
+  "href"
+]
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that ads are created as drafts, that the API emits warnings about automatic field changes, and that Title2 may be merged with Title or dropped depending on the 56-character limit. It also explains the RESPONSIVE_AD combinatorial behavior and the VCard deprecation — behavior an agent cannot infer from annotations alone.

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?

A single dense paragraph that front-loads the creation action and draft status before the alternates and edge-case behaviors. Slightly long, but nearly every clause carries actionable information such as the href requirement and the Title2 merge behavior.

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

Completeness5/5

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

Complete for a mutation tool with no output schema: it covers what gets created (a draft), required linkage (href), the raw_request escape hatch, and the API's warning-based field mutations. Nothing material is left for the agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: why href is required (TextAdAdd needs one of Href/TurboPageId/BusinessId), what VCardId no longer does, and how title2 interacts with title. This goes beyond the schema's simple length constraints.

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?

States a specific verb (creates) and resource (TextAd in an ad group) and clarifies scope against siblings by naming raw_request as the route for BusinessId-based ads and noting VCard is no longer supported. An agent can distinguish this from update_text_ad without opening either schema.

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?

Explicitly routes the agent to raw_request when the ad should use BusinessId instead of a landing page, and states href is mandatory here. It does not explicitly mention update_text_ad for modifications, so it stops short of full when/when-not coverage.

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