Skip to main content
Glama
ssm82

Full VK MCP

vk_users_search

Search VK users by name, location, age, education, and other filters to find matching profiles.

Instructions

Returns a list of users matching the search criteria. VK API method: users.search. Tool name: vk_users_search. Section: users. Access level: read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch query string (e.g., 'Vasya Babich').
sortNoSort order: '1' - by date registered, '0' - by rating
offsetNoOffset needed to return a specific subset of users.
countNoNumber of users to return.
fieldsNoProfile fields to return. Sample values: 'nickname', 'screen_name', 'sex', 'bdate' (birthdate), 'city', 'country', 'timezone', 'photo', 'photo_medium', 'photo_big', 'has_mobile', 'rate', 'contacts', 'education', 'online',
cityNoCity ID.
city_idNoCity ID. Use parameter city instead
countryNoCountry ID.
country_idNoCountry ID. Use parameter country instead
hometownNoCity name in a string.
university_countryNoID of the country where the user graduated.
universityNoID of the institution of higher education.
university_yearNoYear of graduation from an institution of higher education.
university_facultyNoFaculty ID.
university_chairNoChair ID.
sexNo'1' - female, '2' - male, '0' - any (default)
statusNoRelationship status: '0' - Not specified, '1' - Not married, '2' - In a relationship, '3' - Engaged, '4' - Married, '5' - It's complicated, '6' - Actively searching, '7' - In love, '8' - In a civil union
age_fromNoMinimum age.
age_toNoMaximum age.
birth_dayNoDay of birth.
birth_monthNoMonth of birth.
birth_yearNoYear of birth.
onlineNo'1' - online only, '0' - all users
has_photoNo'1' - with photo only, '0' - all users
school_countryNoID of the country where users finished school.
school_cityNoID of the city where users finished school.
school_classNo
schoolNoID of the school.
school_yearNoSchool graduation year.
religionNoUsers' religious affiliation.
companyNoName of the company where users work.
positionNoJob position.
group_idNoID of a community to search in communities.
from_listNo
screen_refNo
from_group_idNo
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It states 'Access level: read', which hints at non-destructive nature, but lacks details on pagination, defaults, rate limits, or response structure. This is adequate but not rich; more context would improve transparency.

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 succinct with three short sentences, front-loading the purpose and including relevant metadata. No redundant or unnecessary information is present.

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 the complexity of 36 parameters and no output schema, the description is too minimal. It does not explain return format, pagination, or how to combine filters effectively. The schema covers parameter details, but the description should provide higher-level usage context.

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 high (89%), so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions; it merely restates the function. Therefore, it does not improve upon the schema's clarity.

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 it returns a list of users matching search criteria, specifying the VK API method 'users.search' and section. Among siblings, this uniquely identifies the tool for user search, distinguishing it from other search tools like vk_groups_search or vk_friends_search.

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 gives no guidance on when to use this tool versus alternatives such as vk_users_get or vk_friends_search. It does not mention prerequisites, limitations, or typical use cases, leaving the agent without decision support for selecting this tool.

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