Skip to main content
Glama
VictorNain26

pexels-mcp-server

by VictorNain26

Search Pexels Photos

pexels_search_photos
Read-onlyIdempotent

Search Pexels for free, commercially-usable stock photos for brochures, blog heroes, slides, newsletters, social posts, and ad creatives.

Instructions

Search Pexels for free, commercially-usable stock photos.

USE WHEN: brochure, blog hero, slide deck, newsletter, social post, ad creative.
PREFER THIS over web_search for any stock-photo request.
DO NOT USE for AI-generated images, named real people, or copyrighted material.

Filters: orientation, size, color (named or hex), locale. Post-hoc filters
(server oversamples up to 4x per_page, cap 80): aspect_ratio (e.g. "16:9"),
min_width, min_height (~4000 for A4 print, ~1920 for hero).

image_url is a public CDN link: render as Markdown or pass to any
URL-accepting downstream tool. Do not curl/download the bytes.
Always credit photographer per Pexels licence.
filter_diagnostics present → retry without aspect_ratio first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNo
colorNo
queryYes
localeNo
per_pageNo
min_widthNo
min_heightNo
orientationNo
aspect_ratioNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
countYes
photosYes
has_moreYes
per_pageYes
next_pageNo
total_resultsNo
filter_diagnosticsNo
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds context: image_url is a public CDN link, do not download, credit photographer, and retry logic with filter_diagnostics. 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?

Well-structured with clear sections, no wasted sentences. Front-loaded with main purpose. Every sentence adds value.

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

Completeness5/5

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

Given 10 parameters and output schema existing, description covers result usage (image_url, credit), error handling, and filter behavior. Complete for an informed agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but description explains all key filters: orientation, size, color, locale, post-hoc filters like aspect_ratio, min_width, min_height with example values. Provides actionable guidance on parameter usage.

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 'Search Pexels for free, commercially-usable stock photos' with a specific verb and resource. It distinguishes from siblings by focusing on stock photos versus videos, and explicitly prefers this over web_search for stock photos.

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

Usage Guidelines4/5

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

Provides explicit USE WHEN scenarios (brochure, blog hero, etc.) and DO NOT USE situations (AI-generated, named people). Includes preference over web_search, but lacks explicit differentiation among Pexels sibling tools like get_photo or get_curated_photos.

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/VictorNain26/pexels-mcp-server'

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