Skip to main content
Glama

Search images

search_images
Read-only

Finds free Pixabay photos, illustrations, and vectors by search term, media type, orientation, and count for coding agents to add relevant visuals to designs and code.

Instructions

Searches free photos, illustrations and vectors on Pixabay. Needs the PIXABAY_API_KEY variable (free key).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNophoto
limitNo
queryYesSearch term (English gives more results)
orientationNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-network profile is partly covered. The description adds genuinely new context by naming the upstream service (Pixabay) and the required PIXABAY_API_KEY variable, which an agent needs before calling. However, it omits rate limits, failure modes when the key is missing, and anything about result shape or attribution.

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?

Two short sentences with the core purpose front-loaded and the prerequisite second; no filler, no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, no-output-schema search tool, the definition covers what it does and the API-key prerequisite but leaves orientation and limit behavior unexplained. An agent could invoke it correctly for a basic query but would be guessing at result shape and pagination/limit semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% – just the query parameter carries a description. The description indirectly covers the type dimension by naming photos, illustrations, and vectors, but says nothing about the limit (max 50) or orientation parameters, nor about the default of "photo". With low coverage the description should have compensated and largely does not.

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?

States a specific verb and resource ("Searches free photos, illustrations and vectors") and names the source (Pixabay), which is enough to separate it from siblings like search_icons or search_fonts. It does not explicitly contrast itself with those siblings, but the media-type wording makes the distinction inferable.

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?

The description says nothing about when to choose this over search_icons, search_components, or other search siblings, and gives no exclusion criteria. The only guidance is the environment prerequisite (PIXABAY_API_KEY), which is setup rather than usage selection.

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