Skip to main content
Glama

Pixabay

by io.github.pipeworx-io

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
NameRequiredDescriptionDefault
qNoSearch term, e.g. "ocean waves". Omitting it returns the generic popular feed, not a search result.
pageNo1-based page number.
orderNopopular (default) | latest
categoryNoSame category list as image search.
per_pageNoResults per page, 3-200 (default 20).
safesearchNo"true" to restrict to videos safe for all ages.
video_typeNoall (default) | film | animation

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description need not repeat those. It adds useful context about the output (stream URLs at multiple resolutions, tags, view counts) and the royalty-free nature of the videos, but does not disclose behavioral details like pagination mechanics or rate limits. With annotations present, this is adequate but not exceptional.

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, front-loaded sentence. It conveys the purpose, scope, and output without any filler or repetition of schema content. Every phrase earns its place.

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 the 7 parameters are fully described in the schema, an output schema exists, and annotations cover safety and world semantics, the description provides enough context for an agent to select and invoke the tool correctly. It clearly communicates the resource and return format without needing to restate structured details.

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 parameters are fully documented in the schema. The description adds a brief summary of the main filter dimensions (keyword, video_type, category, order), which mirrors the schema but helps prioritize. This meets the baseline for high schema coverage; it does not significantly enrich beyond the schema.

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 it searches Pixabay's royalty-free videos with specific filter dimensions (keyword, video_type, category, order) and enumerates the return type (video stream URLs at multiple resolutions, tags, view counts). This goes beyond a generic 'search videos' and distinguishes it from sibling search_images by focusing on videos and their specific output.

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 description implies usage for video search but provides no explicit guidance on when to use this tool versus alternatives like search_images. It does not mention exclusions or provide examples of when to prefer another tool. The context is clear but not elaborated, so it meets the 'implied usage' level.

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

All Pixabay toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation2/5

The tool set contains multiple near-duplicate lookups: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded all do the same routing with minor variations, while deep_research and validate_claim also overlap in information retrieval. The two Pixabay search tools are distinct, but the abundance of overlapping data-lookup tools creates real ambiguity.

Naming Consistency2/5

All names use snake_case, but the pattern is inconsistent: some are verb_noun (search_images, validate_claim), others are noun-based (entity_profile, pipeworx_feedback), and variants like ask_pipeworx_beta/grounded introduce ad-hoc suffixing. The naming does not follow a single predictable convention.

Tool Count1/5

With 33 tools, the count is far excessive for a Pixabay server. Only 2 tools (search_images, search_videos) actually relate to Pixabay; the remaining 31 are unrelated Pipeworx data, Polymarket, memory, and subscription tools. The scope is a severe mismatch.

Completeness1/5

For a server named Pixabay, the surface is severely incomplete: only basic image/video search is provided, with no tool for fetching details, downloading, managing collections, or any other lifecycle operation. Meanwhile, the Pipeworx domain is over-covered, but that is irrelevant to the server's stated purpose.

Resources