Skip to main content
Glama

Search stock media

search_stock
Read-onlyIdempotent

Find stock photos or clips to use as a background 24 results a page. Pass an item's id as look.background.stock_id (source "stock-photo" or "stock-video") or as a Canvas's stock_id to use it instead of the director's pick, and credit the photographer (credit) wherever you show it. orientation: portrait for 9:16 and 1:1, landscape when 16:9 is among the formats (a Canvas is portrait). Clips too short for the loop are left out: pass seconds for a Canvas. thumbnail_url is a 480 px still, preview_url a 1280 px one (the photo, or the clip's poster), preview_video_url a small MP4 of a clip.

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": {
      "kind": "<kind>",
      "q": "<q>"
    },
    "name": "search_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch words, e.g. "foggy pine forest"
kindYesphoto for stock-photo, video for stock-video
pageNoDefault 1; next_page says whether there are more
secondsNoClips for a Canvas of this length (5–8); omit for a Look's loop
orientationNoDefault portrait

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety is covered. The description adds real behavioral detail beyond annotations: 24 results per page and the rule that clips too short for the loop are filtered out, plus what the returned thumbnail/preview URLs represent.

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 purpose is front-loaded and every sentence contributes specific information. It is dense and somewhat run-on in the middle sentence about passing ids, but no sentence is expendable.

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 compensates by explaining the key return fields (thumbnail_url, preview_url, preview_video_url) and page size. It omits explicit mention of next_page, but the schema already documents that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema: orientation is explained in terms of aspect ratios (portrait for 9:16 and 1:1, landscape when 16:9 is among formats) and seconds is tied to excluding clips too short for a Canvas loop.

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 ('Find stock photos or clips to use as a background') with clear scope. No sibling tool overlaps, and the description makes the purpose unmistakable 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 Guidelines4/5

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

Explains how to use results (pass id as look.background.stock_id or a Canvas's stock_id), how orientation maps to formats, and when to pass seconds. It gives clear usage context but does not explicitly exclude alternatives such as upload_background.

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