Unsplash MCP Server

Get Random Photos

get_random_photos

Fetch random Unsplash photos with optional keyword filters. Use for hero images, backgrounds, or when you need variety and want to avoid 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_random_photos"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No	Number of random photos to return, 1-30 (default: 1)
`query`	No	Optional keyword to filter random photos (e.g. "nature", "technology")
`orientation`	No	Filter by orientation - landscape, portrait, squarish
`content_filter`	No	Safety filter - "low" (default) or "high" (stricter)	low

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 29, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It implies a safe read operation via 'Get' and describes randomness, but it does not disclose rate limits, authentication needs, whether results are safe by default, or other operational constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded, short, and mostly free of waste. The second sentence's use cases are helpful, though 'Great for hero images, backgrounds' is slightly marketing-oriented rather than strictly operational.

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?

For a simple read-only photo retrieval tool with complete schema coverage and an output schema, the description covers purpose and key usage context. It could be stronger by explicitly distinguishing from search_photos and noting the content_filter behavior, but it is broadly sufficient.

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 description coverage is 100%, so the schema already documents count, query, orientation, and content_filter. The description only mentions optional keyword filtering and adds no syntax, defaults, or constraint details beyond the schema baseline.

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 clearly states the verb, resource, and source: getting random photos from Unsplash with optional keyword filtering. It is distinguishable from search_photos by emphasizing randomness and variety, though it does not explicitly name that sibling.

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?

It gives clear when-to-use guidance: variety, no specific image in mind, hero images, backgrounds, avoiding repetitive results. It does not explicitly state when to use search_photos instead or name alternative tools, so it falls short of the top score.

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

Deploy Server