Skip to main content
Glama

stock_photos_search

Read-onlyIdempotent

Search a free library of royalty-free stock photos by keyword. It returns real photographs (not AI-generated). Free — no activation required.

Each photo includes a photographer name and source URL. Display attribution somewhere on the page when you use the image.

Example:

{ "project_id": "my-app", "query": "mountain sunset", "per_page": 5 }
// Returns: [{ "url": "https://...", "width": 4000, "height": 2667, "photographer": "Jane Doe", "source_url": "https://..." }, ...]

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": {
      "project_id": "<project_id>",
      "query": "<query>"
    },
    "name": "stock_photos_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number, default 1.
sizeNolarge (24MP+) | medium (12MP+) | small (4MP+).
colorNored, orange, yellow, green, turquoise, blue, violet, pink, brown, black, gray, white, or a hex like "ff5733".
queryYesSearch text, e.g. "mountain sunset" or "office workspace".
per_pageNo1-80, default 15.
project_idYesProject ID (UUID), subdomain, slug, or 'default'. Slug and subdomain are resolved server-side — you don't need to look up the UUID. Searches are attributed to this project's usage.
orientationNolandscape | portrait | square.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, idempotentHint), so the description's job is to add operational context — and it does: free with no activation required, and a mandatory attribution obligation for the photographer. It does not mention rate limits, result caching, or licensing edge cases, which keeps it short of a 5.

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?

Two short front-loaded sentences carry the purpose, licensing, and attribution rule before the example. The JSON example is somewhat long but earns its space by showing the return shape, which is otherwise undocumented.

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?

With no output schema, the description correctly compensates by showing the returned fields (url, width, height, photographer, source_url) in the example. Combined with the attribution requirement and full schema coverage on all seven parameters, an agent has what it needs to call and use results correctly; only pagination behavior and rate limits are unaddressed.

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 every parameter is already documented in the schema, and the description adds no new semantics for query, page, per_page, size, color, or orientation. The example only restates project_id, query, and per_page usage already explained in the schema, so baseline 3 applies.

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?

States a specific verb and resource ("Search a free library of royalty-free stock photos by keyword") and adds a distinguishing qualifier: it returns real photographs, not AI-generated ones, which separates it from the image-generation sibling. An agent can identify this as the photo-lookup tool without opening the schema.

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?

Usage is implied by the framing (free, no activation, real photographs), which hints at when this beats an AI image generator, but no sibling is named and there is no explicit when-to-use/when-not statement. The agent must infer the routing decision from the 'not AI-generated' phrasing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources