Skip to main content
Glama
skiddgoddamn

yandex-marketing-mcp

by skiddgoddamn

yd_metrika_label_unlink

Unlink a Yandex Metrica counter from a label to reorganize your analytics tracking groups.

Instructions

Unlink a counter from a label.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
counter_idYesCounter ID
label_idYesLabel ID
Behavior2/5

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

No annotations provided; description only states the action without disclosing any behavioral traits such as side effects, permissions needed, or reversibility.

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?

Single sentence, no wasted words, appropriately sized for a simple unlink operation.

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

Completeness4/5

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

Given the low complexity (2 parameters, no output schema, no nesting), the description is sufficiently complete for the basic operation, though it could mention what happens if the link doesn't exist.

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 covers 100% of parameters with descriptions, so baseline is 3. Description adds no additional meaning beyond what the schema already provides for counter_id and label_id.

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?

Description clearly states the action 'Unlink a counter from a label', using a specific verb and resource, and distinguishes itself from related siblings like yd_metrika_label_link and yd_metrika_label_delete.

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?

No guidance on when to use this tool vs alternatives (e.g., when to unlink vs delete a label), nor any prerequisite conditions or exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/skiddgoddamn/yandex-marketing-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server