yandex-direct

yd_search

Read-only

Search Yandex Direct API actions by intent using natural language queries. Find relevant API operations for campaigns, ads, keywords, and more.

Instructions

Найти действия Yandex Direct API по намерению. Вызывай первым.

Args: query: что нужно сделать (на русском или английском) domain: фильтр домена (campaigns, adgroups, ads, keywords, bidding, assets, audience, negkeywords, feeds, creatives, research, changes, account, leads, turbopages, reports) limit: максимум результатов (по умолчанию 10)

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": {
      "query": "<query>"
    },
    "name": "yd_search"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`domain`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 28, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The annotation indicates readOnlyHint=true, and the description aligns by describing a search (read) operation. The description adds no further behavioral details beyond the annotation, so it does not significantly enhance transparency.

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 concise, front-loading the core purpose and usage hint, followed by parameter descriptions. Every sentence is necessary and adds value with no redundancy.

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

Completeness4/5

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

Given the tool's simplicity (3 parameters, read-only, output schema present), the description covers purpose, usage order, and parameter meanings. It could include a brief example but overall is sufficient for correct invocation.

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 description coverage is 0%, so the description must explain parameters. It does so clearly: query ('what needs to be done'), domain (lists possible values), limit (maximum results). This adds meaningful context beyond the schema's type/default values.

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 clearly states the tool's purpose: 'Find Yandex Direct API actions by intent.' The verb 'find' and resource 'actions' are specific. The hint 'Call first' distinguishes it from the sibling tool 'yd_execute' by implying a discovery-first workflow.

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?

The description explicitly advises 'Call first,' indicating it should be used before 'yd_execute.' It provides context for when to use it (search by intent) but does not explicitly exclude scenarios where it should not be used or mention alternatives.

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

Deploy Server