Skip to main content
Glama
ssm82

Full VK MCP

by ssm82

vk_photos_get_all

Retrieve photos from a VK user or community in reverse chronological order. Supports detailed info, sizes, and filtering by albums.

Instructions

Returns a list of photos belonging to a user or community, in reverse chronological order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
owner_idNoID of a user or community that owns the photos. Use a negative value to designate a community ID.
extendedNo'1' - to return detailed information about photos
offsetNoOffset needed to return a specific subset of photos. By default, '0'.
countNoNumber of photos to return.
photo_sizesNo'1' - to return image sizes in [vk.com/dev/photo_sizes|special format].
no_service_albumsNo'1' - to return photos only from standard albums, '0' - to return all photos including those in service albums, e.g., 'My wall photos' (default)
need_hiddenNo'1' - to show information about photos being hidden from the block above the wall.
skip_hiddenNo'1' - not to return photos being hidden from the block above the wall. Works only with owner_id>0, no_service_albums is ignored.
Behavior3/5

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

Discloses reverse chronological order, which is a behavioral trait. However, it does not mention pagination (offset/count), authentication needs, or that it retrieves all photos (pagination may limit). With no annotations, more behavior details are expected.

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?

Single sentence, front-loaded with verb and resource, no redundant information. Efficient.

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?

Despite 8 parameters and no output schema or annotations, the description is too brief. It lacks information on pagination, what 'a list' means regarding total counts, and return structure, making it incomplete for an AI agent to use effectively.

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?

All 8 parameters have schema descriptions (100% coverage), so the description adds minimal value beyond the schema. It does provide the ordering detail ('reverse chronological') not in schema, justifying a baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns a list of photos for a user or community in reverse chronological order, which distinguishes it from siblings like vk_photos_get that target specific photos or albums. However, it does not explicitly say 'all' photos, leaving ambiguity about scope.

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 siblings like vk_photos_get or vk_photos_get_albums. The description does not exclude any contexts or mention prerequisites.

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