Skip to main content
Glama
askads

Yandex Direct MCP

by askads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Наборы быстрых ссылок

get_sitelinks
Read-onlyIdempotent

Fetches quick link sets by ID to inspect or verify the sitelinks attached to ads, using SitelinkSetId values from ad records.

Instructions

Читает наборы быстрых ссылок по id. API требует id наборов — их можно взять из поля SitelinkSetId объявлений.

Input Schema

NameRequiredDescriptionDefault
idsYesId наборов быстрых ссылок (обязательны по требованию API).
limitNoМаксимум объектов на страницу.
offsetNoСмещение постраничной выдачи.
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. Changed3 schema fields changedv1.5.1
    • changedInput schema / properties / ids / description
      Previous value: -"Sitelink set ids (required by the API)."New value: +"Id наборов быстрых ссылок (обязательны по требованию API)."
    • changedInput schema / properties / limit / description
      Previous value: -"Max objects per page."New value: +"Максимум объектов на страницу."
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset."New value: +"Смещение постраничной выдачи."
  3. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / limit / maximum
      Previous value: -10000New value: +1000
  4. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, openWorld=true and destructive=false, so the safety profile is covered. The description adds the API's mandatory-id constraint, but says nothing about pagination behaviour (limit/offset) or how the sets are returned, which is the remaining behavioral gap.

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 tightly packed sentences with the core action first and the prerequisite second; nothing is wasted. It is arguably too terse for a tool an agent may need to page through, but there is no filler.

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 simple read-only lookup with rich schema descriptions and full annotations, the description is adequate. The main omission is that there is no output schema and the description doesn't indicate the shape of the returned sitelink sets or how pagination results accumulate.

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 including limit, offset and client_login is already documented. The description only reinforces that ids are mandatory and hints at their source, which is marginal added value beyond the schema — baseline 3 applies.

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?

States a specific verb and resource ('Читает наборы быстрых ссылок по id'), and the id-based lookup distinguishes it from create_sitelinks_set and delete_sitelinks in the sibling list. It doesn't explicitly name those siblings, so differentiation is implied rather than stated.

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?

Adds one genuinely useful usage fact: the API requires ids, and they come from the SitelinkSetId field of ads. That covers the main prerequisite, but there is no explicit when-to-use/when-not statement or reference to alternatives such as raw_request for bulk retrieval.

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