Skip to main content
Glama
vuluu2k

WebCake Landing MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_images

Read-only

Searches Pexels stock photos (API: https://www.pexels.com/api/documentation/) by short English subject queries. Each photo includes hotlinkable URLs at several sizes, a sizes map with each variant's pixel dimensions, avg_color, and the…

Instructions

Searches Pexels stock photos (API: https://www.pexels.com/api/documentation/) by short English subject queries. Each photo includes hotlinkable URLs at several sizes, a sizes map with each variant's pixel dimensions, avg_color, and the photographer's name and attribution URL; the response also includes a size_guide mapping slot widths to variants (hero/banner ~940–1880px → large/large2x, card ~350px → medium, avatar → tiny). queries: [...] runs several searches in parallel and returns { queries: { [q]: result } } — pick:'best' (default) keeps only the top photo per query, pick:'all' the full list; query runs a single search. Works without configuration through a shared hosted proxy; a PEXELS_API_KEY env var or x-pexels-key header uses a personal Pexels quota.

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; returns the full result.
queriesNoSeveral subject queries (typically one per image slot), run in parallel in one call.
per_pageNoPhotos per query (default 5).
orientationNoPreferred shape — 'landscape' for heroes/banners, 'portrait' for tall cards, 'square' for icons/avatars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.11
    • changedInput schema / properties / queries / description
      Previous value: -"Multiple subject queries (one per image slot) to run in parallel — recommended for a page with 2+ images so each only costs ONE round-trip."New value: +"Several subject queries (typically one per image slot), run in parallel in one call."
    • changedInput schema / properties / query / description
      Previous value: -"Single subject query — backward-compat. Prefer `queries` when the page needs 2+ images."New value: +"Single subject query; returns the full result."
  2. First observedv1.5.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint. The description adds crucial behavioral context: the default shared proxy works without configuration, and a PEXELS_API_KEY or x-pexels-key header uses a personal quota. It also details the response structure (hotlinkable URLs, sizes map, avg_color, size_guide), which is essential without an output schema.

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?

Front-loads the purpose and remains information-dense with no filler sentences. It is a single long paragraph rather than a bulleted list, which slightly hurts scanability, but every sentence contributes relevant detail.

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?

With no output schema, the description fully covers the return shape (photo fields, `sizes` map, `avg_color`, attribution, `size_guide`, and the parallel-search response envelope). It also addresses authentication modes. An agent has everything needed to call and interpret results.

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 meaningful detail beyond schema descriptions: the interaction between `pick` and `queries` (best limits to top photo, all returns full list), the parallel behavior of `queries`, and the practical size_guide mapping to slot widths.

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 ('Searches') and resource ('Pexels stock photos') and distinguishes the operation from all siblings, which cover different resources like icons, pages, and uploads. An agent can immediately tell this is the stock-photo search tool.

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 when to use `queries` (multiple slots in parallel), `query` (single search), and `pick:'best'` vs `pick:'all'`, giving clear operational context. It does not explicitly exclude or compare against sibling tools, but no true alternative for stock photo search exists among them.

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

Deploy Server

Other Tools