Skip to main content
Glama
ssm82

Full VK MCP

vk_wall_get_comments

Retrieve comments from a VK user or community wall post. Specify the post ID and optionally filter by sort order, pagination, like counts, and thread items.

Instructions

Returns a list of comments on a post on a user wall or community wall. VK API method: wall.getComments. Tool name: vk_wall_get_comments. Section: wall. Access level: read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
owner_idNoUser ID or community ID. Use a negative value to designate a community ID.
post_idNoPost ID.
need_likesNo'1' - to return the 'likes' field, '0' - not to return the 'likes' field (default)
start_comment_idNo
offsetNoOffset needed to return a specific subset of comments.
countNoNumber of comments to return (maximum 100).
sortNoSort order: 'asc' - chronological, 'desc' - reverse chronological
preview_lengthNoNumber of characters at which to truncate comments when previewed. By default, '90'. Specify '0' if you do not want to truncate comments.
extendedNo
fieldsNo
comment_idNoComment ID.
thread_items_countNoCount items in threads.
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions 'Access level: read,' indicating it's a read operation, but does not disclose pagination behavior, rate limits, or error scenarios. Adequate but minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (three sentences) and front-loaded with the core purpose. However, it could include more detail without becoming 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?

With 12 parameters and no output schema or annotations, the description should provide more behavioral context (e.g., pagination, default values, return structure). It is incomplete for a complex tool.

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 coverage is 75%, so many parameters are already documented. The description does not add extra meaning beyond the schema, providing no additional context for parameters like 'smart' sort or 'extended' field.

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 tool returns a list of comments on a post, specifying the resource (comments) and context (user or community wall). It distinguishes itself from sibling tools like vk_wall_get (which returns posts) and vk_photos_get_comments.

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?

No guidance on when to use this tool versus alternatives, nor any prerequisites or limitations mentioned. The description lacks context for selection.

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