Skip to main content
Glama
cevatkerim

unsplash-mcp

get_random_photos

Retrieve random Unsplash photos for varied imagery, filtered by keyword or orientation. Ideal for backgrounds or avoiding repetitive results.

Instructions

Get random photos from Unsplash, optionally filtered by keyword.

Use this tool when you need variety or don't have a specific image in mind. Great for hero images, backgrounds, or when you want to avoid repetitive results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional keyword to filter random photos (e.g. "nature", "technology")
countNoNumber of random photos to return, 1-30 (default: 1)
orientationNoFilter by orientation - landscape, portrait, squarish
content_filterNoSafety filter - "low" (default) or "high" (stricter)low

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description bears full burden. Mentions random nature and optional filters but lacks details on side effects, rate limits, or auth requirements. Adequate for a simple read tool but could be more informative.

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?

Three sentences, front-loaded with core function. Every sentence adds value: purpose, usage guidance, and differentiation. No wasted words.

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?

Output schema exists, so return values are covered. Description explains randomness, optional keyword, and suitable use cases. Lacks details on error handling or count limits, but overall sufficient for intended use.

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. Description only adds that query is a keyword filter; other parameters (count, orientation, content_filter) are left to schema. No additional meaningful context beyond 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?

Description clearly states verb 'Get random photos' and resource 'from Unsplash', with optional keyword filter. Distinguishes from sibling 'search_photos' by emphasizing variety and lack of specific intent.

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?

Explicitly suggests use cases (hero images, backgrounds) and when to use (variety, no specific image). Implicitly contrasts with search_photos for specific needs, though no direct 'do not use when' clause.

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/cevatkerim/unsplash-mcp'

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