yandex-api-mcp

Overview Schema Source Related Servers Discussions Admin

direct.hf.find_ads

Read-onlyIdempotent

Find Yandex Direct ads by campaign or ad group, status, title, and href filters. Use it to locate specific ad creatives for audits or reporting.

Instructions

Human-friendly: find ads by campaign/adgroup and title/href filters.

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": "direct.hf.find_ads"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`statuses`	No
`account_id`	No	Project profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
`adgroup_id`	No
`campaign_id`	No
`adgroup_name`	No
`campaign_name`	No
`href_contains`	No
`title_contains`	No
`direct_client_login`	No	Override Direct Client-Login for this call (agency multi-project support).

Output Schema

Name	Required	Description	Default
`meta`	Yes
`tool`	Yes
`error`	No
`result`	No
`status`	Yes
`choices`	No
`message`	No
`preview`	No
`warnings`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 29, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds only the 'human-friendly' framing and filter capability, with no mention of pagination, limit defaults, or result-count behavior. Adequate but not rich given the lower bar set by annotations.

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 front-loaded sentence with no wasted words. It is efficient, though the brevity contributes to the parameter gaps.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile. However, for a 10-parameter tool with 20% schema coverage, the description omits too many filter and override parameters to be fully actionable.

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?

Only 20% of the 10 parameters carry schema descriptions, so the description must compensate, yet it only gestures at campaign/adgroup and title/href filters. It never clarifies limit, statuses, name-vs-id precedence, or the direct_client_login override, leaving most parameters undocumented in either place.

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 ('find ads') with the filter dimensions it operates on (campaign/adgroup, title/href). It is distinguishable in spirit from siblings like find_campaigns and find_adgroups, though it never names them explicitly to route the agent.

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?

The description implies when to use it (to locate ads by campaign/adgroup or title/href) but gives no explicit when-not guidance, no prerequisite context, and no reference to alternatives such as direct.list_ads.

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

Deploy Server