Skip to main content
Glama
bulatko

vk-mcp-server

by bulatko

Search communities

vk_groups_search
Read-onlyIdempotent

Search for communities by keyword. Filter results by type, country, city, or sort order to find groups, pages, or events.

Instructions

Find communities by keyword, optionally narrowed by type, country, city or sort order. Returns matches with a total count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query
sortNoSort order: 0 — default, 1 — by speed, 6 — by likes
typeNoCommunity type: group, page or event
countNoNumber of results (max 1000)
fieldsNoAdditional community fields to return
futureNoFilter future events: 1 — only future events
offsetNoOffset for pagination
city_idNoCity ID to filter by
country_idNoCountry ID to filter by

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoTotal number of matches on VK, which is usually larger than the returned page
itemsYesMatching communities
paginationNoWhere this page sits in the whole result. Call the tool again with offset set to next_offset to continue; when next_offset is null there is nothing left to fetch.
Behavior3/5

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

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive. Description adds that it returns matches with a total count, but does not disclose pagination behavior or rate limits. Given annotations, this is adequate but not exceptional.

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?

The description is two sentences, zero wasted words, front-loaded with the main action. Every sentence adds value.

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?

With output schema present, return values are covered. The description mentions optional narrowing and total count, covering most parameter intentions. However, it could briefly note that offset and count control pagination.

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?

Schema description coverage is 100%, so baseline is 3. The description lists several parameters (keyword, type, country, city, sort) but adds no additional meaning beyond the schema's own 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?

Description clearly states the verb 'Find' and resource 'communities', and specifies filtering by keyword, type, country, city, or sort order. This distinguishes it from sibling tools like vk_groups_get which retrieve groups by ID rather than search.

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

Usage Guidelines3/5

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

The description implies usage for searching with optional filters but does not explicitly state when not to use this tool or mention alternatives among siblings (e.g., vk_groups_get for direct lookup). No exclusions or context for when to choose this over other group tools are provided.

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/bulatko/vk-mcp-server'

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