Skip to main content
Glama
askads

VK Ads MCP

Create ad group

create_ad_group

Create an ad group within a VK Ads plan by specifying targeting, budget, dates, and objective. Configure pricing and auction mode for optimized delivery.

Instructions

Creates an ad group inside an ad plan. Targeting goes in targetings (e.g. {"geo":{"regions":[188]},"age":{"age_list":[25,26]}}). Money fields are in account currency. Use extra for any other field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAd group name.
extraNoExtra fields merged into the body verbatim.
priceNoPrice per optimized event, in account currency.
dateEndNoEnd date YYYY-MM-DD.
adPlanIdYesParent ad plan id.
maxPriceNoBid cap in account currency.
dateStartNoStart date YYYY-MM-DD.
objectiveNoGroup objective, e.g. site_conversions, leadads, traffic.
targetingsNoTargeting structure, sent verbatim.
budgetLimitNoTotal budget in account currency.
budgetLimitDayNoDaily budget in account currency.
autobiddingModeNoAuction strategy, e.g. max_goals.
Behavior4/5

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

Annotations indicate mutation (readOnlyHint=false) and openWorldHint=true. Description adds context on targeting format, currency, and extra field merging, which is beyond annotation details.

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-load the purpose, then provide critical usage details. No wasted words.

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?

Covers main usage points despite no output schema and complex parameters. Could mention return value, but not required and still complete for invocation.

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?

With 100% schema coverage, baseline is 3. Description adds value by explaining targeting structure with an example, money field currency, and the extra field's role, improving over schema descriptions.

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 states 'Creates an ad group inside an ad plan' with a clear verb and resource. It distinguishes from siblings like update_ad_group and list_ad_groups.

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?

Provides specific guidance on targeting structure, money field currency, and the extra field. Lacks explicit when-not-to-use or alternatives, but creation context is clear.

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/askads/mcp-vk-ads'

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