Skip to main content
Glama
bulatko

vk-mcp-server

by bulatko

List community members

vk_groups_get_members
Read-onlyIdempotent

Retrieve members of a VK community. Returns user IDs or selected profile fields, but many communities hide their member list, leading to an access error.

Instructions

List the members of a community. Returns bare user IDs unless you ask for fields, in which case it returns profiles. Many communities hide their member list, which comes back as an access error rather than an empty list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order: id_asc, id_desc, time_asc, time_desc
countNoNumber of members to return (max 1000)
fieldsNoAdditional profile fields to return (e.g. photo_200,online,sex,city)
filterNoFilter: managers, editors, mods, advertisers, friends, unsure
offsetNoOffset for pagination
group_idYesCommunity ID or its short name (e.g. apiclub). Positive and without the minus sign — the minus belongs to owner_id on a wall, not here.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoTotal number of matches on VK, which is usually larger than the returned page
itemsYesMember IDs, or profiles when fields are requested
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.
Behavior4/5

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

Annotations (readOnlyHint, idempotentHint) already indicate safe, idempotent behavior. The description adds value by revealing that hidden member lists return an access error instead of an empty list, and that output format depends on fields parameter.

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 extremely concise: two sentences, no wasted words. The first sentence states the action, the second adds essential nuance. Perfectly front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (so return values are documented) and comprehensive annotations, the description covers all needed context: default output, parameter effects, and error behavior. It is complete for an agent to use correctly.

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 coverage is 100%, but the description adds meaning beyond the schema: it clarifies the default output (bare user IDs) and the role of the 'fields' parameter. It also provides a crucial note about group_id format ('Positive and without the minus sign').

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 title 'List community members' and description clearly state the tool's purpose: listing members of a community. It specifies the output (bare user IDs or profiles) and distinguishes from tools like vk_groups_get by focusing on members.

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 does not explicitly state when to use this tool versus alternatives, but it provides a key behavioral note about hidden member lists causing errors. This implies caution but lacks direct usage guidance or exclusions.

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