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

yandex-direct-mcp-plus

by Pavelsiba

Создать быстрые ссылки

set_sitelinks

Creates a new set of 1–8 quick links for an ad and returns the set ID for attachment. Use it to prepare quick links before linking them to a Yandex.Direct ad.

Instructions

Создать новый набор из 1–8 быстрых ссылок. Возвращает ID набора для привязки к объявлению.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sitelinks": "<sitelinks>"
    },
    "name": "set_sitelinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
sitelinksYesНовый набор из 1–8 быстрых ссылок

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.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world operation, so the safety profile is covered. The description adds two useful behavioral facts — the 1–8 item bound and that an ID is returned for later attachment — but says nothing about idempotency, whether existing sets are affected, or what happens when the limit is exceeded.

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 sentences, zero filler, with the creation action and the return value front-loaded. Nothing could be removed without losing information.

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?

For a single-parameter mutation with full schema documentation and safety annotations, the description covers creation and the returned ID. It falls short on the attachment workflow — the sibling tool that binds the returned ID to an ad is never named — and on the absence of an output schema, which the description only partially compensates for.

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

Parameters2/5

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

Schema coverage is 100% and the single nested array already documents title, href, and description with length limits. The description repeats the 1–8 cardinality already encoded in minItems/maxItems and adds no meaning about individual fields, so it contributes essentially nothing beyond the schema.

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?

The description names a specific verb and resource ('Создать новый набор из 1–8 быстрых ссылок') and states the return value, so the create semantics of the ambiguous name 'set_sitelinks' are resolved. It does not explicitly contrast with sibling mutations like add_ad_extensions or with list_sitelinks/delete_sitelinks, but the operation is unambiguous.

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?

Usage is only implied: the phrase 'для привязки к объявлению' hints that a set is created first and attached afterward, but no alternative tool is named and no condition for choosing this over list_sitelinks or add_ad_extensions is given. An agent can infer the workflow but must guess the follow-up call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.