Skip to main content
Glama

unsplash_get_photo

Read-onlyIdempotent

Retrieve a single Unsplash photo by its ID, returning image URLs and attribution details for proper use.

Instructions

Get a single Unsplash photo by id (URLs + attribution).

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": {
      "access_key": "<access_key>",
      "photo_id": "<photo_id>"
    },
    "name": "unsplash_get_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
photo_idYesUnsplash photo id
access_keyYesUnsplash Access Key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful return context ('URLs + attribution'), but does not discuss auth expectations beyond the schema's access_key field or error behavior for invalid ids.

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 no wasted words. It communicates the core action, lookup key, and return content efficiently.

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 lookup with complete schema and annotation coverage, the description is largely sufficient, especially since it sketches the return content. It could be slightly more complete by naming alternatives or clarifying invalid-id behavior, but nothing critical is missing.

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 both photo_id and access_key are already documented. The description reinforces that lookup is by id but adds no format or semantic detail beyond the schema.

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: get a single Unsplash photo by id. The phrase 'single ... by id' implicitly distinguishes it from sibling search and random-photo tools, though it does not name them explicitly.

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

Usage Guidelines3/5

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

The 'by id' wording implies the tool should be used when a photo id is known, but it gives no explicit when-not guidance or alternatives such as unsplash_search_photos or unsplash_random_photo.

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

Deploy Server

Other Tools