Pixabay

Search Videos

search_videos

Read-onlyIdempotent

Search Pixabay's library of royalty-free videos by keyword, video_type, category, or order; returns video stream URLs at multiple resolutions (large, medium, small, tiny), tags, and view counts.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Search term, e.g. "ocean waves". Omitting it returns the generic popular feed, not a search result.
`page`	No	1-based page number.
`order`	No	popular (default) \| latest
`category`	No	Same category list as image search.
`per_page`	No	Results per page, 3-200 (default 20).
`safesearch`	No	"true" to restrict to videos safe for all ages.
`video_type`	No	all (default) \| film \| animation

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "_apiKey": "your-pixabay-api-key",
-    "q": "nature wildlife"
-  },
-  {
-    "_apiKey": "your-pixabay-api-key",
-    "per_page": 15,
-    "q": "ocean waves"
-  }
-]New value: +[
+  {
+    "q": "nature wildlife"
+  },
+  {
+    "per_page": 15,
+    "q": "ocean waves"
+  }
+]

Changed8 schema fields changedAug 1, 2026

removedInput schema / additionalProperties
```
Removed value: -true
```

addedInput schema / properties / category

Added value: +{
+  "description": "Same category list as image search.",
+  "type": "string"
+}

addedInput schema / properties / order

Added value: +{
+  "description": "popular (default) | latest",
+  "type": "string"
+}

addedInput schema / properties / page

Added value: +{
+  "description": "1-based page number.",
+  "type": "number"
+}

addedInput schema / properties / per_page

Added value: +{
+  "description": "Results per page, 3-200 (default 20).",
+  "type": "number"
+}

addedInput schema / properties / q

Added value: +{
+  "description": "Search term, e.g. \"ocean waves\". Omitting it returns the generic popular feed, not a search result.",
+  "type": "string"
+}

addedInput schema / properties / safesearch

Added value: +{
+  "description": "\"true\" to restrict to videos safe for all ages.",
+  "type": "string"
+}

addedInput schema / properties / video_type

Added value: +{
+  "description": "all (default) | film | animation",
+  "type": "string"
+}

First observedMay 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds useful output context (stream URLs at multiple resolutions, tags, view counts), but does not disclose behaviors like the popular-feed fallback when q is omitted or any pagination behavior. Since annotations carry much of the burden, a 3 is appropriate.

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 dense sentence with no wasted words. It front-loads the resource and the searchable dimensions, then states the key return values. Every element earns its place.

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?

For a read-only search tool with rich annotations, a complete input schema, and an output schema, the description conveys the essential purpose, filter dimensions, and return shape. Minor behavioral context such as the popular-feed fallback when q is omitted is left to the schema, which is acceptable here, though a one-phrase note about that fallback would make it fully self-contained.

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 100%, so the schema fully documents all 7 parameters. The description adds only a handful of parameter names without additional semantic detail, which is exactly the baseline case where 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 states a specific action ('Search'), a concrete resource ('Pixabay's library of royalty-free videos'), and the main filter dimensions (keyword, video_type, category, order). It is clearly a video-search tool, though it does not explicitly contrast itself with sibling search_images or search_within, so it stops just short of full differentiation.

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?

Usage is implied by the tool name and the description ('Search Pixabay's library of royalty-free videos'), and the listed filter fields make it clear this is for video discovery. However, the description gives no explicit when-to-use or when-not-to-use guidance, and does not name alternatives such as search_images or search_within.

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

All Pixabay 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.