Skip to main content
Glama
bulatko

vk-mcp-server

by bulatko

Delete a post

vk_wall_delete
Destructive

Delete a VK wall post permanently. Provide the post ID; optionally specify owner ID for community (negative) or user (positive) walls.

Instructions

Delete a post from a wall. owner_id is negative for a community. This cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYesPost ID to delete
owner_idNoWall owner: a community as a negative number (-123), a person as a positive one. Defaults to the token owner.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether VK accepted the change
Behavior4/5

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

Annotations already mark destructiveHint=true. Description adds that deletion 'cannot be undone', reinforcing the destructive nature and clarifying context (owner_id negative for community). No contradictions.

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: first states core action, second adds essential nuance. No fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Simple two-parameter tool with output schema present (though not shown). Description sufficiently covers deleting a post; no obvious 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 description coverage is 100%, baseline 3. Description adds meaning by explaining owner_id sign convention (negative for community) and default behavior (token owner), going beyond the 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?

Description clearly states the action ('Delete a post') and resource ('from a wall'), and specifies the owner_id convention. It distinguishes from sibling tools like vk_wall_get, vk_wall_post, vk_wall_edit by focusing on deletion.

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

Usage Guidelines3/5

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

Description mentions irreversibility and owner_id sign convention, but does not explicitly state when to use this tool vs alternatives (e.g., for permanent removal vs hiding or editing), nor provide exclusion criteria.

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/bulatko/vk-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server