Skip to main content
Glama

Pixabay Search Images

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

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "sunset beach"
    },
    "name": "pixabay_search_images"
  }
}

Input 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Search term, e.g. \"red panda\". THE subject of the request — omitting it returns Pixabay's generic popular feed, not a search result."New value: +"Search term, e.g. \"red panda\". THE subject of the request, omitting it returns Pixabay's generic popular feed, not a search result."
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds a modest amount beyond that by noting the response includes multi-size URLs, tags, likes, and download counts, but says nothing about rate limits, API-key needs, or result caps.

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?

A single front-loaded sentence with the verb and resource first, followed by filters and return shape. No filler, no repetition of the title.

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 12 fully documented parameters, no required fields, an output schema, and safety annotations already in place, the description does enough for an agent to call it correctly. Only operational details (pagination expectations, external API constraints) are absent, which is minor here.

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 100%, so the baseline is 3; however the description groups the filters into a coherent sentence (keyword, image_type, category, orientation, colors, order) that helps an agent recognize the faceting model at a glance. It does not add syntax or default details beyond the schema, so it stays below 5.

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 gives a specific verb and resource ("Search Pixabay's library of royalty-free photos and illustrations") and enumerates the filter dimensions, so an agent can tell what the tool retrieves. It does not explicitly contrast itself with siblings such as search_videos, relying on the media-type wording to differentiate.

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

Usage Guidelines2/5

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

It states what can be searched but never says when to reach for this tool versus alternatives, nor any exclusions, prerequisites, or cost/rate considerations. An agent must infer that this is the tool for finding stock imagery.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.