Skip to main content
Glama

Search stock photos

search_stock_photos

Search free stock photos (Pexels + Pixabay) by keyword. Returns url, thumbnailUrl and author; pass a url in mediaUrls of create_post / create_draft_post when the user has no media of their own. Requires the MEDIA_READ scope.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the notable extras: two external providers, the required MEDIA_READ scope, and the returned fields. It omits how many results are returned, whether results are paginated or randomized, and any licensing/attribution obligations that Pexels and Pixabay typically impose.

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 short sentences, front-loaded with purpose, then return values, then the concrete follow-up action. Nothing is redundant and every clause adds an operative fact.

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?

Because there is no output schema, the description usefully enumerates url, thumbnailUrl and author. For a single-parameter search tool it covers purpose, auth scope, and next step; only result-count/pagination behavior 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?

There is one parameter with 0% schema description coverage, so the description must compensate. 'By keyword' does add the semantic that query is free-text search terms rather than an ID, but gives no guidance on length, phrase behavior, or what happens on empty results despite schema constraints of 1-200 chars.

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 ('Search free stock photos') and names the upstream providers (Pexels + Pixabay), so the agent knows exactly what comes back. It is implicitly distinguished from list_media via 'when the user has no media of their own', but it never names that sibling directly.

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?

Gives a clear triggering condition ('when the user has no media of their own') and even explains the downstream step: pass a returned url into mediaUrls of create_post / create_draft_post. It stops short of an explicit negative rule such as 'do not use this to browse the user's existing library'.

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