Skip to main content
Glama
ssm82

Full VK MCP

vk_wall_get_comments

Retrieve comments from a VK wall post. Filter by owner, post, sort order, and include likes or thread details.

Instructions

Returns a list of comments on a post on a user wall or community wall.

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.
Behavior2/5

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

No annotations provided, so description must cover behavior. It does not mention pagination, sorting, or that empty lists can be returned. Lacks disclosure of important traits.

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?

Single sentence is concise but omits key context (e.g., required parameters). Could be expanded moderately 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?

Given 12 parameters, no output schema, and no annotations, the description is too minimal. It does not explain how to use parameters or interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description adds no parameter-specific meaning beyond the input schema. With 75% schema coverage, it does not compensate for the 25% missing descriptions.

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?

Clear verb 'Returns a list' and specific resource 'comments on a post on a user wall or community wall'. Distinguishes from sibling vk_wall_get_comment which returns a single comment.

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 vs alternatives like vk_wall_get_comment or vk_photos_get_comments. Does not mention required parameters or scenario.

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