Pexels

Video Popular

video_popular

Read-onlyIdempotent

Fetch Pexels' popular video feed; returns paginated video objects with file URLs at multiple resolutions, duration, and videographer info.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No
`page`	No	Current page number
`videos`	No	Array of popular video objects
`per_page`	No	Number of results per page
`next_page`	No	URL for next page of results
`total_results`	No	Total number of results available

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedJun 2, 2026
- changedOutput schema / properties / page / type
```
Previous value: -"integer"New value: +"number"
```
- changedOutput schema / properties / per_page / type
```
Previous value: -"integer"New value: +"number"
```
- changedOutput schema / properties / total_results / type
```
Previous value: -"integer"New value: +"number"
```
- addedOutput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / videos / items / properties / avg_color / type
```
Previous value: -"string"New value: +"null"
```
- changedOutput schema / properties / videos / items / properties / duration / type
```
Previous value: -"integer"New value: +"number"
```
- addedOutput schema / properties / videos / items / properties / full_res
```
Added value: +{
+  "type": "null"
+}
```
- changedOutput schema / properties / videos / items / properties / height / type
```
Previous value: -"integer"New value: +"number"
```
- changedOutput schema / properties / videos / items / properties / id / type
```
Previous value: -"integer"New value: +"number"
```
- addedOutput schema / properties / videos / items / properties / tags
```
Added value: +{
+  "items": {},
+  "type": "array"
+}
```
- changedOutput schema / properties / videos / items / properties / user / properties / id / type
```
Previous value: -"integer"New value: +"number"
```
- addedOutput schema / properties / videos / items / properties / video_files / items / properties / file_type
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / videos / items / properties / video_files / items / properties / fps
```
Added value: +{
+  "type": "number"
+}
```
- changedOutput schema / properties / videos / items / properties / video_files / items / properties / height / type
```
Previous value: -"integer"New value: +"number"
```
- changedOutput schema / properties / videos / items / properties / video_files / items / properties / id / type
```
Previous value: -"integer"New value: +"number"
```
- addedOutput schema / properties / videos / items / properties / video_files / items / properties / size
```
Added value: +{
+  "type": "number"
+}
```
- removedOutput schema / properties / videos / items / properties / video_files / items / properties / type
```
Removed value: -{
-  "description": "File type (e.g., video/mp4)",
-  "type": "string"
-}
```
- changedOutput schema / properties / videos / items / properties / video_files / items / properties / width / type
```
Previous value: -"integer"New value: +"number"
```
- addedOutput schema / properties / videos / items / properties / video_pictures
```
Added value: +{
+  "items": {
+    "properties": {
+      "id": {
+        "type": "number"
+      },
+      "nr": {
+        "type": "number"
+      },
+      "picture": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
```
- removedOutput schema / properties / videos / items / properties / video_subtitles
```
Removed value: -{
-  "description": "Available subtitle files",
-  "type": "array"
-}
```
- changedOutput schema / properties / videos / items / properties / width / type
```
Previous value: -"integer"New value: +"number"
```
First observedMay 25, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds valuable behavior beyond that: it returns paginated results, with file URLs at multiple resolutions, duration, and videographer info. This enriches the agent's understanding of the operation without contradicting the 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?

The description is a single sentence that front-loads the action ('Fetch Pexels' popular video feed') and packs useful details (paginated, file URLs, resolutions, duration, videographer info) without wasted words. It is appropriately concise for the tool's simplicity.

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?

For a parameterless, read-only tool with an output schema and comprehensive annotations, the description is complete. It states what the tool does and what the response contains (paginated video objects with key properties). No additional context seems necessary for an agent to select and invoke it correctly.

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?

The tool has zero parameters, so the baseline of 4 applies. There is no parameter meaning to explain, and the description does not need to compensate for schema coverage. The description shifts focus to the output format, which is fine.

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 fetches Pexels' popular video feed with a specific verb and resource, and the 'popular feed' scope differentiates it from search and specific video tools in the sibling list. However, it does not explicitly name alternatives or contrast with them, so it falls short of a 5.

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

Usage Guidelines3/5

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

The use case is implied: call this tool to get popular videos. But there are no explicit when-to-use/when-not-to-use instructions or references to alternative tools (e.g., video_search). The usage context relies on the name and description rather than explicit guidance.

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

All Pexels tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.