Skip to main content
Glama

Layero

by ru.layero.mcp
OverviewDiscussionsAdmin
This connector has been deprecated

Duplicate listing of the same server under an old namespace. The maintained listing is Layero (ru.layero/layero): same endpoint https://mcp.layero.ru/mcp, current description and tools. The landing-page generator described here was removed in MCP 2.0.

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

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
NameRequiredDescriptionDefault
branchNoThe branch whose traffic is counted. Defaults to the production branch; pass it only when the user asks to track a preview branch.
projectYesThe project: its slug (`my-site`) or id, as listed by `my_projects`. The site address works too (`https://clear-garden-vypm.layero.app` or just `clear-garden-vypm`) — note that the address host is NOT always the slug.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYes
connectedYes
oauth_urlNo
counter_idNo
next_actionYes
injection_modeNo
tracked_branchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / branch / description
      Previous value: -"Ветка, трафик которой считать. По умолчанию — основная; указывай, только если пользователь просит считать превью-ветку."New value: +"The branch whose traffic is counted. Defaults to the production branch; pass it only when the user asks to track a preview branch."
    • changedInput schema / properties / project / description
      Previous value: -"Проект: слаг (`my-site`) или id. Слаг — то, что видно в адресе сайта; если пользователь назвал сайт словами, возьми слаг из `my_projects`."New value: +"The project: its slug (`my-site`) or id, as listed by `my_projects`. The site address works too (`https://clear-garden-vypm.layero.app` or just `clear-garden-vypm`) — note that the address host is NOT always the slug."
  2. Changed2 schema fields changed
    • addedInput schema / properties / branch / description
      Added value: +"Ветка, трафик которой считать. По умолчанию — основная; указывай, только если пользователь просит считать превью-ветку."
    • addedInput schema / properties / project / description
      Added value: +"Проект: слаг (`my-site`) или id. Слаг — то, что видно в адресе сайта; если пользователь назвал сайт словами, возьми слаг из `my_projects`."
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses key behavioral traits beyond the openWorldHint annotation: the authorization requires user action in a browser, the tool returns a link to show the user, and checking later is done differently. This meaningfully informs the agent how the operation actually behaves.

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 compact and well-structured: a one-sentence purpose, then the crucial browser-authorization warning, then follow-up instructions. Every sentence earns its place, and critical operational guidance is prominently placed and emphasized.

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 tool's moderate complexity, the description covers everything an agent needs: the auth limitation, the returned link, the no-polling rule, and how to check status later. Since an output schema exists, the description does not need to enumerate return values and remains complete.

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 fully explains both `project` and `branch`. The description adds one practical detail about omitting `branch` for later checks, but it does not redefine or enrich the parameter semantics beyond that. Baseline 3 is appropriate.

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 states a specific action and resource: 'Connect Yandex Metrika to a site.' This clearly identifies the tool's purpose and differentiates it from siblings like site_analytics and read_site, which are about reading or checking data rather than establishing the connection.

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 gives practical usage guidance: it warns that authorization happens in a browser, tells the agent not to poll in a loop, and directs follow-up checks through the same tool without the branch argument or via site_analytics. It stops short of an explicit when-not-to-use statement, but the context is clear.

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

All Layero toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources