Skip to main content
Glama
ssm82

Full VK MCP

vk_groups_get_members

Retrieve a list of community members from VK groups with sorting, filtering, and field customization options.

Instructions

Returns a list of community members. VK API method: groups.getMembers. Tool name: vk_groups_get_members. Section: groups. Access level: read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idNoID or screen name of the community.
sortNoSort order. Available values: 'id_asc', 'id_desc', 'time_asc', 'time_desc'. 'time_asc' and 'time_desc' are availavle only if the method is called by the group's 'moderator'.id_asc
offsetNoOffset needed to return a specific subset of community members.
countNoNumber of community members to return.
fieldsNoList of additional fields to be returned. Available values: 'sex, bdate, city, country, photo_50, photo_100, photo_200_orig, photo_200, photo_400_orig, photo_max, photo_max_orig, online, online_mobile, lists, domain, has_mobile, contacts, connections, site, education, universities, schools, can_post, can_see_all_posts, can_see_audio, can_write_private_message, status, last_seen, common_count, relation, relatives, counters'.
filterNo*'friends' - only friends in this community will be returned,, *'unsure' - only those who pressed 'I may attend' will be returned (if it's an event).
Behavior2/5

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

With no annotations, the description carries the burden of behavioral disclosure. It states 'Access level: read', which indicates a non-destructive operation. However, it does not mention pagination, rate limits, error behavior, or the effect of parameters like 'filter' on the response. Minimal transparency beyond basic safety.

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 short (two sentences) but includes redundant information: the VK API method name, tool name, and section. The first sentence clearly states purpose, but the second sentence could be omitted as it repeats the tool name and adds the section. Slightly inefficient but not excessively verbose.

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 there is no output schema, the description should have explained what the tool returns (e.g., a list of user IDs or user objects). It does not mention the response structure, pagination behavior, or any limitations such as maximum members returned. The parameters are well-defined, but the overall context of the tool's output is missing.

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 schema has 100% coverage, with each parameter described in detail including defaults, enums, and constraints. The description adds no additional meaning beyond what is already in the schema. For example, 'group_id' is described as 'ID or screen name of the community', which matches the schema. No extra value is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns a list of community members, which is a specific verb and resource. It is distinct from sibling tools like vk_groups_get (which returns group info) and vk_groups_is_member (which checks individual membership). However, it does not specify what information is returned for each member, such as user IDs or profiles.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It only notes an access level of 'read', which implies safety but does not exclude use cases or mention other tools for checking membership or requesting members. Sibling tools exist for related purposes, but no differentiation is offered.

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