Skip to main content
Glama
ssm82

Full VK MCP

vk_photos_get_all

Retrieve all photos from a VK user or community in reverse chronological order. Supports filtering by album type and hidden status.

Instructions

Returns a list of photos belonging to a user or community, in reverse chronological order. VK API method: photos.getAll. Tool name: vk_photos_get_all. Section: photos. Access level: read.

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

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

With no annotations, the description carries the full burden. It mentions the tool is read-only ('Access level: read') and the sort order, but lacks details on pagination, rate limits, or return format. Important behavioral traits are missing.

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 concise, with the main purpose in the first sentence. However, it includes redundant metadata (VK API method, tool name, section) that could be omitted or integrated.

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 8 parameters and no output schema, the description is incomplete. It does not discuss pagination, maximum count, or how the extended parameter works. The agent would need additional context for effective use.

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 detailed descriptions in the input schema (100% coverage), so the description adds no extra parameter information. Baseline 3 is appropriate as the schema does the heavy lifting.

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 the tool returns a list of photos for a user or community in reverse chronological order, identifying the resource and operation. However, it does not differentiate from sibling tools like vk_photos_get or vk_photos_get_user_photos, so it lacks distinctiveness.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It implies usage for retrieving all photos but does not exclude other tools for specific albums or scenarios.

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