Skip to main content
Glama
vuluu2k

WebCake Landing MCP

by vuluu2k

search_images

Read-only

Search Pexels stock photos by subject queries and retrieve hotlinkable image URLs with multiple sizes, color, and photographer attribution for landing page image slots.

Instructions

Searches Pexels stock photos (see https://www.pexels.com/api/) by short English subject queries. Returns hotlinkable URLs at several sizes, avg_color for matching section backgrounds, plus photographer name and attribution URL. PICK BY SIZE, NOT JUST TOPIC: each photo carries a sizes map (delivered WxH px per variant) and the response includes a size_guide — match the variant width to the slot's rendered width (hero/banner → src.large ~940px or src.large2x ~1880px retina; card/thumb → src.medium ~350px; avatar → src.tiny), because a too-small variant stretched across a big slot pixelates ('vỡ ảnh') and src.original / an oversized variant in a small card bloats the page ('nặng trang'). BATCH MODE: pass queries: [...] to fetch multiple subjects in PARALLEL — e.g. ['fresh coffee cup','barista pouring','interior cafe'] for hero + about + gallery — returns { queries: { [q]: result } } so the caller picks one image per slot in a single round-trip; default pick='best' returns only the top photo per query (compact, drop-in for specials.src), pick='all' returns the full list. query (single) returns the full result like before. Works out of the box via a shared hosted proxy; set PEXELS_API_KEY env or x-pexels-key header to use your own quota. ONLY for image slots with NO source image: when the user supplied images or the reference HTML/URL contains image URLs (ingest AST images/background_images/og_image), re-host THOSE via upload_images instead of searching stock photos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page for pagination (default 1).
pickNoWith `queries`, 'best' (default) returns only the top photo per query (compact, drop-in for specials.src); 'all' returns the full result. Single-query calls always return the full result.
sizeNoMinimum photo size to return (default any).
colorNoOptional color filter: a name (red, blue, …) or a hex like '6a8f3c'.
queryNoSingle subject query — backward-compat. Prefer `queries` when the page needs 2+ images.
queriesNoMultiple subject queries (one per image slot) to run in parallel — recommended for a page with 2+ images so each only costs ONE round-trip.
per_pageNoPhotos per query (default 5).
orientationNoPreferred shape — 'landscape' for heroes/banners, 'portrait' for tall cards, 'square' for icons/avatars.
Behavior5/5

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

Adds context beyond annotations: explains the use of a hosted proxy, optional API key, sizing guidelines to avoid pixelation or bloat, and pick behavior. No contradictions with readOnlyHint and openWorldHint.

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?

Long but well-structured with clear sections (sizing, batch mode, exclusions). Front-loaded with main purpose. Every sentence adds value, though could be slightly trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive coverage for a tool with 8 parameters and no output schema. Explains response fields, sizing strategy, authentication, and when to avoid use. Fills gaps left by missing output schema.

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% with descriptions. The description adds extra context for parameters like pick, queries, and orientation, such as suggesting when to use batch mode and size selection tips. Baseline 3 raised to 4 due to added value.

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?

The description clearly specifies the tool searches Pexels stock photos by English subject queries, returns hotlinkable URLs, avg_color, and photographer info. It distinguishes from sibling tools like upload_images and get_icon_svg by stating when to use each.

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

Usage Guidelines5/5

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

Explicitly states when to use (image slots with no source image) and when not (use upload_images if user supplies images). Also provides guidance on batch mode with queries parameter for multiple images.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vuluu2k/webcake-landing-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server