yandex-api-mcp

Overview Schema Source Related Servers Discussions Admin

dashboard.generate_option1

Idempotent

Generate an HTML and JSON dashboard combining Yandex Direct and Metrica data for a chosen date range, with optional goals, Wordstat, and audience segments.

Instructions

Generate a simple HTML+JSON dashboard from Direct+Metrica data (Option 1).

Input Schema

TableJSON Schema

Name	Required	Description
`date_to`	Yes	YYYY-MM-DD.
`goal_ids`	No	Optional Metrica goal IDs. When set, dashboard will include leads based on goal{ID}reaches (best effort).
`date_from`	Yes	YYYY-MM-DD.
`account_id`	No	Project profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
`counter_id`	No	Metrica counter id (optional if account profile has exactly one).
`output_dir`	No	When set, write HTML+JSON files to this directory.
`account_ids`	No	Optional explicit list of account profile ids to include in a multi-account dashboard.
`return_data`	No	Return the full data payload in response (default: false if output_dir is set, otherwise true).
`all_accounts`	No	When true, generate one dashboard containing data for all configured account profiles (account switcher in UI).
`include_html`	No	Include HTML content in response (default: true if output_dir is not set).
`dashboard_slug`	No	Optional suffix for output file names.
`include_audience`	No	Include Audience segments blocks (default: false).
`include_wordstat`	No	Include Wordstat suggestions block (default: false).
`wordstat_devices`	No	Optional Wordstat devices filter.
`wordstat_regions`	No	Optional Wordstat region ids.
`wordstat_language`	No	Negative lexicon language ru\|en (default: ru).
`direct_client_login`	No	Override Direct Client-Login for this call (agency multi-project support).
`include_raw_reports`	No	Include raw Direct/Metrica payloads in output data (default: true).
`wordstat_num_phrases`	No	Wordstat numPhrases (default: 50, max: 2000).
`wordstat_max_campaigns`	No	Max campaigns to analyze with Wordstat (default: 5).
`wordstat_max_negatives_per_campaign`	No	Max negative tokens per campaign (default: 25).
`wordstat_max_candidates_per_campaign`	No	Max Wordstat candidates per campaign (default: 20).
`wordstat_max_seed_phrases_per_campaign`	No	Max seed phrases per campaign (default: 3).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations only declare readOnlyHint=false and idempotentHint=true; the description adds nothing about the main behavioral traits an agent needs: that it writes files to disk when output_dir is set, that it makes outbound Direct/Metrica/Wordstat calls, or the cost/quota implications of the many optional Wordstat blocks.

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 short sentence with no filler, appropriately front-loaded with the action and artifact. It is efficient but arguably too terse given the tool's complexity.

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

Completeness2/5

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

For a 23-parameter tool that produces files and aggregates two data sources plus optional Wordstat/Audience blocks, one sentence is insufficient. An output schema exists so return values need not be explained, but the description should at minimum distinguish this from the pro dashboard sibling and note the file-writing behavior.

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 all 23 parameters (including defaults for output_dir, return_data, include_html, wordstat_* limits) are already documented in the schema. The description contributes no additional parameter semantics beyond naming the data sources, so the 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 ('Generate'), the artifact ('simple HTML+JSON dashboard') and the data sources ('Direct+Metrica data'), so the agent knows what it produces. However, '(Option 1)' merely restates the tool name and gives no clue how this differs from the sibling dashboard.generate_pro_html.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all. The parenthetical '(Option 1)' implies an alternative exists, but the description never names dashboard.generate_pro_html or states the condition under which the simple variant is preferred over the pro one.

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

Deploy Server