pexels-mcp-server

Get Pexels Collection Contents

pexels_get_collection_media

Read-onlyIdempotent

Retrieve photos and videos from a Pexels collection by providing its collection ID. Filter results by media type, dimensions, aspect ratio, and sort order.

Instructions

Read the photos + videos inside a Pexels collection.

USE WHEN you have a collection id (pexels.com/collections/<id>).
Filter to one type with `type` ('photos' or 'videos').
Post-hoc filters (aspect_ratio, min_width, min_height) apply to both.
DO NOT USE for discovery — no public list-all-collections endpoint.

Per-item shape matches the search tools.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection_id": "<collection_id>"
    },
    "name": "pexels_get_collection_media"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`sort`	No
`type`	No
`per_page`	No
`min_width`	No
`min_height`	No
`aspect_ratio`	No
`collection_id`	Yes

Output Schema

Name	Required	Description	Default
`id`	Yes
`page`	Yes
`count`	Yes
`photos`	Yes
`videos`	Yes
`has_more`	Yes
`per_page`	Yes
`next_page`	No
`total_results`	No
`filter_diagnostics`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Jul 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds that per-item shape matches search tools and that filters apply to both types, providing useful behavioral context beyond annotations without contradiction.

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?

Seven lines of concise, front-loaded text. Every sentence adds value: purpose, usage condition, filter guidance, exclusion, and matching note. No wasted words.

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?

Output schema exists, so return values are handled. Covers key parameters and usage constraints. Mentions per-item shape matches search tools for familiarity. Lacks detail on pagination but sufficient given standard expectations.

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?

Schema description coverage is 0%, so description must compensate. Mentions collection_id, type, aspect_ratio, min_width, min_height (4 of 8 parameters). Misses page, per_page, sort. Partial compensation, adequate but not complete.

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 'Read the photos + videos inside a Pexels collection' with specific verb and resource. Implicitly distinguishes from discovery tools by requiring collection_id and explicitly advising against discovery use.

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

Usage Guidelines5/5

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

Explicitly says 'USE WHEN you have a collection id' and 'DO NOT USE for discovery — no public list-all-collections endpoint.' Provides clear context for when to use and when to avoid, including mention of filters and matching search tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server