pexels-mcp-pro

Preview photos by id

preview_photos

Fetch inline thumbnails for photo IDs from prior searches, preserving API quota. Increase height to inspect finalists more closely.

Instructions

Fetch inline thumbnails for specific photo #ids (from earlier searches — costs no API quota for already-seen ids). Use a larger height for a closer look at finalists.

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": {
      "ids": "<ids>"
    },
    "name": "preview_photos"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes
`height`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, description adds key behavior: 'costs no API quota for already-seen ids'. However, it does not disclose return format, error handling, or authorization requirements. Some behavioral insight but incomplete.

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?

Two sentences, front-loaded with action and context, then parameter guidance. No redundant words. Efficient and clear.

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?

Given low complexity (2 params, no output schema, no annotations), description covers purpose, usage context, and parameter behavior. Lacks explicit return format and alternative tool comparisons, but sufficient for basic use.

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 coverage is 0%, so description must add meaning. It implies ids are from earlier searches and height affects magnification. Provides functional context but no details on min/max, default, or types beyond schema.

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?

Description states 'Fetch inline thumbnails for specific photo #ids', specifying verb (fetch) and resource (inline thumbnails for photos by ids). It distinguishes from siblings like get_media and download_media by focusing on thumbnails and the context of earlier searches.

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?

Implies usage after search_photos with 'from earlier searches' and 'finalists'. Guides parameter use ('Use a larger height for a closer look at finalists'). Does not explicitly exclude alternative tools, but context is clear.

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

Deploy Server