Skip to main content
Glama
VK Ads MCP

VK Ads MCP

Информация об аккаунте

get_user_info
Read-onlyIdempotent

Retrieve current VK Ads account details, including client name, to verify which advertiser account your token targets and confirm that you are accessing the intended client cabinet.

Instructions

Возвращает информацию о текущем аккаунте VK Рекламы (user.json), включая additional_info.client_name. Позволяет убедиться, на какой аккаунт рекламодателя указывает токен. Токен гранта client_credentials агентского аккаунта видит объекты самого агентства, а не его клиентов: кабинет клиента открывает только токен гранта agency_client_credentials в VK_ADS_TOKEN.

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": "get_user_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoПоля пользователя в ответе. По умолчанию — базовый набор.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.0
    • changedInput schema / properties / fields / description
      Previous value: -"User fields to return. Defaults to a common set."New value: +"Поля пользователя в ответе. По умолчанию — базовый набор."
  2. First observedv1.1.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, but the description adds genuinely non-obvious context: an agency client_credentials token sees the agency's own objects, not its clients', so the tool can return unexpected data. It does not cover error behavior for an invalid token, but the grant-scoping nuance is substantive.

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?

Three sentences, front-loaded with what is returned, then the use case, then the caveat that explains surprising output. No filler or restatement of the tool name.

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?

There is no output schema, so the description carrying the key return field (additional_info.client_name) is helpful, and the token-grant caveat covers the main source of confusion. Minor gap: no mention of what happens with an invalid or expired token.

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?

There is a single optional parameter (fields) with 100% schema coverage, so the schema already explains it. The description never mentions the field-selection behavior, adding nothing beyond the schema; the baseline of 3 applies.

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?

A specific verb plus resource: it returns info about the current VK Ads account (user.json), naming a concrete returned field (additional_info.client_name). It is clearly distinguishable from sibling auth_status/get_balance because it states the account-identity purpose explicitly.

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?

It gives an explicit use case: verifying which advertiser account the token points to, plus the condition that determines the answer (grant type of the token). It does not name alternatives such as auth_status or get_balance, so there is no when-not guidance, 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.