Skip to main content
Glama

Pixabay

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Images

search_images
Read-onlyIdempotent

Search Pixabay's library of royalty-free photos and illustrations by keyword, image_type, category, orientation, colors, or order; returns URLs in multiple sizes, tags, likes, and download counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch term, e.g. "red panda". THE subject of the request — omitting it returns Pixabay's generic popular feed, not a search result.
pageNo1-based page number.
orderNopopular (default) | latest
colorsNoComma-separated: grayscale, red, orange, yellow, green, turquoise, blue, lilac, pink, white, gray, black, brown, transparent
categoryNoe.g. backgrounds, nature, science, education, people, animals, travel, business, music
per_pageNoResults per page, 3-200 (default 20).
min_widthNoMinimum image width in px.
image_typeNoall (default) | photo | illustration | vector
min_heightNoMinimum image height in px.
safesearchNo"true" to restrict to images safe for all ages.
orientationNoall (default) | horizontal | vertical
editors_choiceNo"true" to restrict to Editor's Choice.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -true
    • addedInput schema / properties / category
      Added value: +{
+  "description": "e.g. backgrounds, nature, science, education, people, animals, travel, business, music",
+  "type": "string"
+}
    • addedInput schema / properties / colors
      Added value: +{
+  "description": "Comma-separated: grayscale, red, orange, yellow, green, turquoise, blue, lilac, pink, white, gray, black, brown, transparent",
+  "type": "string"
+}
    • addedInput schema / properties / editors_choice
      Added value: +{
+  "description": "\"true\" to restrict to Editor's Choice.",
+  "type": "string"
+}
    • addedInput schema / properties / image_type
      Added value: +{
+  "description": "all (default) | photo | illustration | vector",
+  "type": "string"
+}
    • addedInput schema / properties / min_height
      Added value: +{
+  "description": "Minimum image height in px.",
+  "type": "number"
+}
    • addedInput schema / properties / min_width
      Added value: +{
+  "description": "Minimum image width in px.",
+  "type": "number"
+}
    • addedInput schema / properties / order
      Added value: +{
+  "description": "popular (default) | latest",
+  "type": "string"
+}
    • addedInput schema / properties / orientation
      Added value: +{
+  "description": "all (default) | horizontal | vertical",
+  "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. \"red panda\". THE subject of the request — omitting it returns Pixabay's generic popular feed, not a search result.",
+  "type": "string"
+}
    • addedInput schema / properties / safesearch
      Added value: +{
+  "description": "\"true\" to restrict to images safe for all ages.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, lowering the bar. The description adds context by naming the external source (Pixabay) and the nature of returned data (URLs, tags, likes, download counts), which is useful for the agent. It does not mention API key requirements, but the openWorldHint annotation flags external access.

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 with no fluff. It packs the action, resource, key filters, and return types into about 25 words, earning its place with useful information.

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?

With a well-documented 12-parameter schema, an existing output schema, and clear annotations, the description is adequately complemented by structured metadata. It adds necessary orientation for selecting the tool and mentions return payload components. The only minor gap is the lack of explicit note on API key usage, but the schema examples contain '_apiKey'.

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?

The input schema already provides 100% description coverage for all 12 parameters, so the baseline is 3. The description's enumeration of filter dimensions (keyword, image_type, category, orientation, colors, order) is a redundant high-level summary, not adding new meaning beyond what the schema already specifies.

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 the verb 'Search' and the specific resource (Pixabay's library of royalty-free photos and illustrations), and differentiates the tool from siblings like search_videos by naming its content type and search dimensions. It lists filterable attributes and return fields, making the tool's scope unmistakable.

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?

The description gives clear context for when to use the tool (searching images on Pixabay) but does not explicitly mention alternatives or exclusion cases. The differentiation from search_videos is implied by the resource and content type, but not spelled out as a recommendation.

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

Resources