Skip to main content
Glama
ssm82

Full VK MCP

vk_photos_get_wall_upload_server

Obtain the upload server address needed to post a photo to a VK wall. Use this address to upload the photo file, then save it to the wall.

Instructions

Returns the server address for photo upload onto a user's wall. VK API method: photos.getWallUploadServer. Tool name: vk_photos_get_wall_upload_server. Section: photos. Access level: read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idNoID of community to whose wall the photo will be uploaded.
Behavior2/5

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

Without annotations, the description only says it returns a server address; it does not disclose side effects, permissions, rate limits, or behavior when group_id is omitted.

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?

The description is somewhat verbose, repeating the tool name and API method; it could be more concise by omitting redundant details.

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

Completeness3/5

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

The description is adequate for a simple tool, but lacking output schema, it does not describe the return value format; completeness is minimal.

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?

The schema covers the parameter fully, and the tool description does not add extra meaning beyond what the schema provides; baseline 3 for high coverage.

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 server address for photo upload onto a user's wall, distinguishing it from other upload server tools like chat or market album.

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 is provided on when to use this tool versus alternatives; the description does not differentiate from similar tools like vk_photos_get_chat_upload_server.

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