Skip to main content
Glama

image_search

Read-onlyIdempotent

Search for images using descriptive queries with filters for size, type, color, and format. Returns image URLs, thumbnails, and metadata.

Instructions

Find images by query with filters for size, type, color, and format. Returns JSON with fields: images (array of {title, link, thumbnailLink, displayLink, contextLink, width, height, fileSize}), query, resultCount. Results sorted by relevance; max 10 per call, no pagination. On no matches returns resultCount: 0 with empty array; on failure returns isError with message. Subject to per-tenant rate limit (default 30 req/min) with automatic provider fallback. Use this for visual assets or image references — not for text information. Use web_search for pages containing images, or scrape_page to extract images from a known URL. Results cached 30 min.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesDescriptive search query for images (e.g. 'golden retriever puppy playing fetch'). More descriptive = better results.,required
num_resultsNoNumber of image results (1-10, default: 5).
sizeNoFilter by image size: huge, icon, large, medium, small, xlarge, xxlarge.
typeNoFilter by image type: clipart, face, lineart, stock, photo, animated.
color_typeNoFilter by color mode: color, gray, mono, trans (transparent background).
dominant_colorNoFilter by dominant color: black, blue, brown, gray, green, orange, pink, purple, red, teal, white, yellow.
file_typeNoFilter by file format: jpg, gif, png, bmp, svg, webp.
safeNoSafeSearch level: off, medium (default), high.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagesNo
queryNo
resultCountNo
Behavior5/5

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

Annotations already indicate safe read-only operation. Description adds significant behavioral context: return structure, error handling, caching, rate limits, and provider fallback. No contradiction with annotations.

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 concise yet comprehensive, front-loaded with purpose, and each sentence adds value (return format, behavior, error handling, alternatives). No wasted words.

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 tool's complexity (8 params, 1 required) and rich schema/annotations/output schema presence, the description covers all necessary context: usage, return values, error states, performance (caching, rate limits), and alternatives.

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 coverage is 100%, so baseline is 3. The description groups filters and explains the return format but does not add substantial meaning beyond the schema descriptions for individual parameters.

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 tool's purpose: 'Find images by query with filters for size, type, color, and format.' It distinguishes from siblings by explicitly stating 'Use web_search for pages containing images, or scrape_page to extract images from a known URL.'

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use: 'Use this for visual assets or image references — not for text information.' and mentions alternatives for other use cases. Also includes context like max 10 results per call and rate limits.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zoharbabin/web-researcher-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server