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

yandex-direct-mcp-plus

by Pavelsiba

Список визиток

list_vcards
Read-only

Retrieve Yandex.Direct virtual business cards by ID or find cards linked to ads in selected campaigns. Use IDs, campaign filters, and pagination to inspect available cards.

Instructions

Получить виртуальные визитки по ID или найти их через объявления выбранных кампаний. Создавать визитки Директ через API не даёт — новая визитка заводится в интерфейсе Директа.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_vcards"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoСколько объектов вернуть (максимум 10000)
offsetNoСмещение выборки: сюда передаётся LimitedBy предыдущей страницы
vcard_idsNoКонкретные визитки по их ID
campaign_idsNoНайти визитки, привязанные к объявлениям этих кампаний

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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
  2. First observedv1.6.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful behavioral constraint the annotations do not convey: vcards cannot be created through the API, so the agent should not attempt a write path. It says nothing about pagination or result volume, which is the remaining gap.

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, both front-loaded and free of filler. The primary retrieval capability comes first and the API-creation limitation follows as a supporting constraint.

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 read-only list tool with full annotation and schema coverage, the description is adequate. However, there is no output schema, so a brief indication of what a returned vcard contains (or how results are paged) would round it out; that omission is the main shortfall.

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%, and the schema already documents limit, offset, vcard_ids and campaign_ids, including the note that offset takes LimitedBy from the previous page. The description's phrasing of the two selection modes largely restates what the schema says, adding little new meaning beyond the schema baseline.

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 states a specific verb and resource (get virtual vcards) and names the two retrieval modes: by ID or through ads of selected campaigns. It does not explicitly contrast with the sibling delete_vcards, but the added note that creation is impossible via API sharpens the tool's scope considerably.

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?

It clearly maps the two ways to call the tool (vcard_ids vs campaign_ids) and tells the agent that creating a vcard is not an option here — it must be done in the Direct interface. There is no explicit routing to delete_vcards, but the when-to-use context is otherwise unambiguous.

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