Layero

Подключить Яндекс.Метрику

connect_analytics

Connect Yandex Metrika to a site.

IMPORTANT: authorisation happens IN A BROWSER, and neither you nor the
platform can do that step for the user. The tool returns a link — show
it and ask them to open it and grant access. Do not poll in a loop: the
person may walk away for an hour. Check later through this same tool
without the `branch` argument, or through `site_analytics`.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`branch`	No	Ветка, трафик которой считать. По умолчанию — основная; указывай, только если пользователь просит считать превью-ветку.
`project`	Yes	Проект: слаг (`my-site`) или id. Слаг — то, что видно в адресе сайта; если пользователь назвал сайт словами, возьми слаг из `my_projects`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`project`	Yes
`connected`	Yes
`oauth_url`	No
`counter_id`	No
`next_action`	Yes
`injection_mode`	No
`tracked_branch`	No

TDQS

A4.9/5.0

Behavior5/5

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

The description discloses critical behavioral traits: authorization is browser-based, the tool returns a link, and polling is discouraged. The annotation openWorldHint only hints at external interaction, but the description goes beyond by explaining the exact workflow and state-check method, which is not present in annotations.

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 and well-structured: it opens with the purpose, then highlights the critical browser authorization step, gives clear instructions, and closes with future-checking guidance. Every sentence adds value, with no fluff.

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

Completeness5/5

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

Given the complexity of OAuth flows, the description completely covers what the agent needs to know: it explains the authorization process, return type (link), and how to poll later. The output schema exists, so return details do not need to be repeated. The tool is fully contextualized among siblings.

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?

The input schema already provides parameter descriptions with 100% coverage, so the baseline is 3. The description adds operational meaning by suggesting calling without the branch argument to check status later, which is useful beyond the schema's static definitions.

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 connects Yandex Metrika to a site, which is a specific verb+resource. It distinguishes itself from sibling tools like site_analytics (which likely reads analytics data) by describing the setup/authorization flow.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool (to connect Metrika), warns that authorization happens in a browser, instructs the agent to show the link to the user, and advises against polling. It also mentions checking later via the same tool without the branch argument or via site_analytics, providing clear alternatives.

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

All Layero tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation3/5

Most tools are distinct, but there's real confusion risk between the deploy-related set (cancel_deploy, retry_deploy, deploy_logs, diagnose_deploy) and the site-inspection set (site_status, read_site, site_issues, site_screenshot) where purposes overlap. compose_landing vs compose_landing_submit are differentiated mostly by an obscure note rather than naming. Several tools address similar concepts (landing composition, publishing, deploy) making agent misselection plausible.

Naming Consistency3/5

Most tools use a clean verb_noun pattern (list_deploys, connect_domain, check_domain, publish_landing, read_site, rollback). However, conventions are mixed: some use compose/x/check/y (check_copy, check_domain, check_performance) while others use site_x (site_status, site_analytics, site_issues, site_screenshot) with inconsistent ordering. Descriptions mix English and Russian heavily, though that's content not naming.

Tool Count4/5

27 tools is a large but arguably justified surface for a full site-building/deploying/monitoring platform spanning composition, domain management, deploys, performance, analytics, and environment configuration. It sits slightly above what feels tight, but each tool has a defined role in the overall workflow.

Completeness4/5

The surface covers the full landing lifecycle: compose, publish, deploy, monitor, rollback, diagnose, and connect external resources (domain, analytics, integrations). Minor gaps: no explicit tool for site deletion/teardown, only read_site for editing with refactor_site being narrow, and no way to update an existing landing's text beyond refactor. Still, core CRUD and operational flows are covered.

Resources

Need Help?