Skip to main content
Glama
Sign In
yandex-api-mcp

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

direct.hf.attach_sitelinks_to_ads

Attach an existing sitelinks set to Yandex Direct ads so they show extra links, with dry-run preview and apply options.

Instructions

Human-friendly: attach an existing sitelinks set to ads.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "direct.hf.attach_sitelinks_to_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
applyNo
ad_idsNo
dry_runNo
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
sitelink_set_idNo
direct_client_loginNoOverride Direct Client-Login for this call (agency multi-project support).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 of behavioral disclosure. It implies a mutation ('attach') but does not state permissions required, whether attaching is idempotent, what happens if the sitelink set is already attached, or how dry_run/apply behave. This is far too thin for a write operation with six parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence and front-loaded, which is structurally good. However, the 'Human-friendly:' prefix is filler that does not earn its place, and the sentence is so sparse that it fails to inform rather than being truly concise.

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

Completeness1/5

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

For a six-parameter mutation tool with no annotations and no output schema, the description omits critical context: parameter roles, behavioral effects, safety profile, and usage conditions. It is not complete enough for an agent to invoke the tool correctly without additional inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 33%, so the description must compensate for undocumented parameters, but it adds no parameter-level meaning at all. It does not explain apply, ad_ids, dry_run, or sitelink_set_id, leaving four of six parameters semantically opaque.

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?

The description states a specific verb ('attach') and resource ('an existing sitelinks set to ads'), making the core action clear. It does not explicitly differentiate itself from siblings like attach_callouts_to_ads or attach_vcard_to_ads, though the resource name implicitly distinguishes it. The 'Human-friendly:' prefix adds no clarifying value.

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 guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. An agent must infer usage from the tool name alone. 'Human-friendly' is too vague to count as context.

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