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

yandex-api-mcp

by 5iNeX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

audience.hf.overlap_matrix

Calculate a sparse overlap matrix for given Yandex Audience segment IDs to identify intersecting segments and shared audience sizes.

Instructions

Human-friendly: overlap matrix (sparse) for segment ids.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "segment_ids": "<segment_ids>"
    },
    "name": "audience.hf.overlap_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_kNoDefault: 50.
account_idNoProject profile id (resolves to Direct Client-Login and optional Metrica counter defaults).
segment_idsYes
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 must carry the full behavioral burden. It discloses only that the output is a sparse matrix, without stating whether the operation is read-only, what permissions or account context are needed, how top_k affects results, or what the matrix values represent.

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 definition is a single short sentence and is not verbose, but 'Human-friendly:' is vague filler that does not earn its place. The core information is front-loaded enough to avoid confusion, though the sentence is under-specified rather than efficient.

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?

With no annotations and no output schema, the description should explain the return shape and key behavioral context. It only hints at a sparse overlap matrix, leaving the output format, authentication/account requirements, and comparison semantics undocumented for a 4-parameter analytical tool.

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

Parameters2/5

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

Schema description coverage is 75%, with top_k, account_id, and direct_client_login already documented in the input schema. The description adds only 'for segment ids,' which repeats the required parameter and provides no additional meaning for the remaining parameters or the expected array format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'overlap matrix (sparse) for segment ids' names a resource and input scope, so the general purpose is inferable. However, it lacks a clear verb and does not distinguish this tool from the sibling audience.segments.overlap, leaving ambiguity about what operation is performed.

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 guidance on when to use this tool, when not to use it, or which sibling alternatives exist. The only context is 'for segment ids,' which identifies an input rather than a usage condition.

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