Skip to main content
Glama
VictorNain26

pexels-mcp-server

by VictorNain26

Get Pexels Popular Videos

pexels_get_popular_videos
Read-onlyIdempotent

Fetch trending videos from Pexels for B-roll, ad references, or motion content. Filter by dimensions, duration, or aspect ratio to find suitable clips.

Instructions

Fetch Pexels' trending video feed.

USE WHEN: B-roll inspiration, trending motion content, ad reference.
DO NOT USE for query-specific video search — call pexels_search_videos.

Native Pexels filters (server-side, no oversampling): min_width,
min_height, min_duration (seconds), max_duration (seconds). Post-hoc
(oversampled 4x, cap 80 when set): aspect_ratio. video_url is a
public CDN MP4 link: render as Markdown or pass to any URL-accepting
downstream tool. Do not curl/download the bytes. Credit
uploader_name per Pexels licence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
per_pageNo
min_widthNo
min_heightNo
aspect_ratioNo
max_durationNo
min_durationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
countYes
videosYes
has_moreYes
per_pageYes
next_pageNo
total_resultsNo
filter_diagnosticsNo
Behavior5/5

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

Annotations already include readOnlyHint, openWorldHint, idempotentHint. Description adds important behavioral details: native vs post-hoc filtering (oversampling 4x, cap 80), video_url as public CDN MP4 link, directive not to curl/download, and credit requirement. No contradiction with annotations.

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?

Description is concise (5 sentences), front-loaded with purpose, and every sentence adds value. No unnecessary information or redundancy.

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?

Given 7 parameters and output schema existence, description covers purpose, usage, filter behavior, link handling, and attribution. It omits explicit explanation of page and per_page, but overall provides sufficient context for effective use.

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

Parameters4/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. It explains filter parameters like min_width, min_height, min_duration, max_duration, aspect_ratio (including oversampling behavior). However, pagination parameters (page, per_page) are not described, leaving a minor gap.

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 'Fetch Pexels' trending video feed', which is a specific verb and resource. It explicitly distinguishes from sibling tools by noting not to use for query-specific search and directing to pexels_search_videos.

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 lists use cases (B-roll inspiration, trending motion content, ad reference) and specifies when not to use (query-specific video search), with alternative tool named. Also provides guidance on filters and attribution.

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