Skip to main content
Glama
askads

VK Ads MCP

by askads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Произвольный запрос к API VK Рекламы

raw_request
Destructive

Send direct requests to any VK Ads API endpoint, including those without a dedicated tool. Use query parameters for GET and JSON body for POST; writes require confirmation.

Instructions

Универсальный запрос напрямую к любому эндпоинту API VK Рекламы (например, path "v2/ad_plans.json", method GET). Нужен для эндпоинтов, у которых нет отдельного инструмента. query уходит в строку запроса, body отправляется как JSON для POST. GET выполняется свободно; POST и DELETE — запись, для них нужен confirmWrite=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoJSON-тело для POST-запросов.
pathYesПуть эндпоинта с версией, например "v2/ad_plans.json", "v3/statistics/banners/day.json".
queryNoПараметры строки запроса (фильтры, поля, постраничная выдача).
methodNoHTTP-метод. По умолчанию GET.
confirmWriteNoДолжен быть true для записи (POST или DELETE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.5.0
    • changedInput schema / properties / body / description
      Previous value: -"JSON body for POST requests."New value: +"JSON-тело для POST-запросов."
    • changedInput schema / properties / confirmWrite / description
      Previous value: -"Must be true for a write (POST or DELETE)."New value: +"Должен быть true для записи (POST или DELETE)."
    • changedInput schema / properties / method / description
      Previous value: -"HTTP method. Default GET."New value: +"HTTP-метод. По умолчанию GET."
    • changedInput schema / properties / path / description
      Previous value: -"Versioned endpoint path, e.g. \"v2/ad_plans.json\", \"v3/statistics/banners/day.json\"."New value: +"Путь эндпоинта с версией, например \"v2/ad_plans.json\", \"v3/statistics/banners/day.json\"."
    • changedInput schema / properties / query / description
      Previous value: -"Query string parameters (filters, fields, pagination)."New value: +"Параметры строки запроса (фильтры, поля, постраничная выдача)."
  2. First observedv1.1.3

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already mark it as non-read-only and destructive; the description adds the specific rule that GET is executed freely while POST and DELETE are writes requiring confirmWrite=true, giving context beyond the annotations.

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?

Four concise sentences, front-loaded with the core purpose, and each sentence adds a distinct piece of information without redundancy or fluff.

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?

The description covers purpose, usage condition, parameter handling, and safety requirements. It does not describe the response format, but for a generic raw request without an output schema this is acceptable and not a critical gap.

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

Parameters4/5

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

Schema covers all parameters (100%), and the description adds how `query` maps to the query string and `body` is sent as JSON for POST, enriching the semantics of parameter usage beyond the schema.

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 clearly states it performs a universal request to any endpoint of the VK Ads API and explicitly says it is for endpoints without a dedicated tool, distinguishing it from sibling tools that cover specific resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit condition: use when no separate tool exists, and clarifies that GET is free while POST/DELETE require confirmWrite=true. This is clear guidance on when and how to use it versus the specialized alternatives.

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