Skip to main content
Glama
ssm82

Full VK MCP

vk_groups_search

Search VK communities by keyword and optional filters like type, location, and market. Retrieve matching groups, pages, or events for audience targeting.

Instructions

Returns a list of communities matching the search criteria. VK API method: groups.search. Tool name: vk_groups_search. Section: groups. Access level: read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query string.
typeNoCommunity type. Possible values: 'group, page, event.'
country_idNoCountry ID.
city_idNoCity ID. If this parameter is transmitted, country_id is ignored.
futureNo'1' - to return only upcoming events. Works with the 'type' = 'event' only.
marketNo'1' - to return communities with enabled market only.
sortNoSort order. Possible values: *'0' - default sorting (similar the full version of the site),, *'1' - by growth speed,, *'2'- by the "day attendance/members number" ratio,, *'3' - by the "Likes number/members number" ratio,, *'4' - by the "comments number/members number" ratio,, *'5' - by the "boards entries number/members number" ratio.
offsetNoOffset needed to return a specific subset of results.
countNoNumber of communities to return. "Note that you can not receive more than first thousand of results, regardless of 'count' and 'offset' values."
Behavior2/5

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

With no annotations provided, the description must carry the burden. It states it's read-only but lacks details about pagination, sorting behavior, error handling, or authentication requirements. The behavioral traits beyond the basic read are not disclosed.

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 description is a single sentence plus redundant metadata (tool name, VK method, section). It is not overly long but could be more concise by removing redundant information.

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?

Given 9 parameters and no output schema, the description fails to explain what the returned list contains, how to interpret results, or how parameters interact (e.g., country_id vs city_id). For a search tool, this is insufficient.

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?

The input schema has 100% coverage of parameter descriptions, so the baseline is 3. The description does not add extra meaning beyond the schema; it merely lists generic metadata.

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 'Returns a list of communities matching the search criteria' which is a specific verb+resource. It also distinguishes from sibling tools like vk_groups_get by indicating it's a search operation, and clarifies it's read-only with 'Access level: read'.

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 implicitly suggests usage for searching communities but does not explicitly state when to use this tool over alternatives like vk_groups_get_by_id or vk_groups_get. No 'when not to use' or alternative tool names are given.

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/ssm82/full-vk-mcp'

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