vk-mcp-server

Get user profiles

vk_users_get

Read-onlyIdempotent

Resolve a VK user's screen name to a numeric ID or retrieve profile details. Use this to check if a profile is closed before calling other tools.

Instructions

Look up VK users by numeric ID or short name (e.g. durov). Use this to resolve a name to an ID before calling other tools, or to check whether a profile is closed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	No	Profile fields to return
`user_ids`	No	Comma-separated user IDs or screen names

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No	Total number of matches on VK, which is usually larger than the returned page
`items`	Yes	User profiles
`pagination`	No	Where 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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.1Jul 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of matches on VK, which is usually larger than the returned page",
+      "type": "number"
+    },
+    "items": {
+      "description": "User profiles",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "description": "Where 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.",
+      "properties": {
+        "next_from": {
+          "description": "Cursor for the next page, on the tools that page by cursor rather than offset",
+          "type": "string"
+        },
+        "next_offset": {
+          "description": "Offset for the next page, or null when this page is the last one",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "offset": {
+          "description": "The offset this page started at",
+          "type": "number"
+        },
+        "returned": {
+          "description": "How many came back on this page",
+          "type": "number"
+        },
+        "total": {
+          "description": "How many matches VK has in total",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

First observedv0.1.2Mar 8, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already cover read-only and idempotent hints; description adds behavioral context about checking profile closed status but doesn't elaborate further.

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?

Two concise sentences, front-loaded with action, no unnecessary words.

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 low complexity, existing annotations, and output schema, the description fully covers purpose, usage, and parameter context without gaps.

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% and description adds meaning: user_ids can be numeric IDs or screen names with example 'durov', clarifying usage beyond schema.

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 the verb (look up), resource (VK users by numeric ID or short name), and distinguishes from siblings like vk_users_search.

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

Usage Guidelines4/5

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

Explicitly says when to use: to resolve a name to an ID before calling other tools or check if a profile is closed. Implicitly differentiates from search tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.