Skip to main content
Glama
5iNeX

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

dashboard.generate_pro_html

Generate a Pro HTML+JSON dashboard for Yandex Direct and Metrica, combining search terms, keyword diagnostics, bids, campaign watchlist, and tracking gap findings.

Instructions

Pro-only: generate an enriched HTML+JSON dashboard with search terms, keyword diagnostics, campaign watchlist, bids, and tracking gap findings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_toYesYYYY-MM-DD.
goal_idsNoOptional Metrica goal IDs. When set, dashboard will include leads based on goal{ID}reaches (best effort).
date_fromYesYYYY-MM-DD.
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
counter_idNoMetrica counter id (optional if account profile has exactly one).
output_dirNoWhen set, write HTML+JSON files to this directory.
account_idsNoOptional explicit list of account profile ids to include in a multi-account dashboard.
return_dataNoReturn the full data payload in response (default: false if output_dir is set, otherwise true).
all_accountsNoWhen true, generate one dashboard containing data for all configured account profiles (account switcher in UI).
include_htmlNoInclude HTML content in response (default: true if output_dir is not set).
max_findingsNoMax findings to include in the PRO insights panel (default: 24).
max_keywordsNoMax keyword report rows to parse for PRO insights (default: 100).
max_campaignsNoMax campaigns to include in the PRO watchlist (default: 12).
dashboard_slugNoOptional suffix for output file names.
include_audienceNoInclude Audience segments blocks (default: false).
include_wordstatNoInclude Wordstat suggestions block (default: false).
wordstat_devicesNoOptional Wordstat devices filter.
wordstat_regionsNoOptional Wordstat region ids.
wordstat_languageNoNegative lexicon language ru|en (default: ru).
max_search_phrasesNoMax search phrase report rows to parse for PRO insights (default: 200).
direct_client_loginNoOverride Direct Client-Login for this call (agency multi-project support).
include_raw_reportsNoInclude raw Direct/Metrica payloads in output data (default: false).
wordstat_num_phrasesNoWordstat numPhrases (default: 50, max: 2000).
wordstat_max_campaignsNoMax campaigns to analyze with Wordstat (default: 5).
wordstat_max_negatives_per_campaignNoMax negative tokens per campaign (default: 25).
wordstat_max_candidates_per_campaignNoMax Wordstat candidates per campaign (default: 20).
wordstat_max_seed_phrases_per_campaignNoMax seed phrases per campaign (default: 3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read/generate operation and mentions 'Pro-only', but says nothing about side effects (file writes when output_dir is set), auth/plan requirements behind the Pro gate, or default output location — all of which matter for a 27-parameter generator.

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 dense sentence with the gating constraint ('Pro-only') front-loaded and the content list after it. No filler, though it packs a lot into one line without structure for a 27-param tool.

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 complex 27-parameter generator with no annotations and no output schema, a one-sentence description is thin: it leaves file-writing behavior, response shape (HTML vs JSON vs both), and the distinction from dashboard.generate_option1 unexplained.

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 the schema already documents all 27 parameters (defaults, formats, dependencies). The description adds only the content categories, not syntax or default behavior, so baseline 3 is appropriate when the schema does the heavy lifting.

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) and a well-scoped resource (enriched HTML+JSON dashboard) and enumerates its contents: search terms, keyword diagnostics, campaign watchlist, bids, tracking gaps. The 'Pro-only' qualifier hints at a tier difference, but it never names or contrasts with the sibling dashboard.generate_option1, so the agent must infer which dashboard to pick.

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 explicit when-to-use guidance and no exclusion rules. The presence of dashboard.generate_option1 as a sibling makes the missing routing guidance costly — nothing tells the agent when the Pro variant is the right choice over the base variant.

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