Skip to main content
Glama
Sign In
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_images

Read-only

Find stock photos for storefront pages or products and return WebCake CDN-ready URLs, re-hosting Pexels results so raw links display correctly.

Instructions

Search stock photos (Pexels) for a page/product. IMPORTANT: the storefront only renders images served from the WebCake CDN (image domains are whitelisted) — raw Pexels URLs will NOT display. By default this re-hosts each result on the WebCake CDN and returns a ready-to-use cdn_url (cached, so repeats are free). Use cdn_url for image src / product images. Requires the PEXELS_API_KEY environment variable.

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_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSubject to search, e.g. 'coffee shop interior'
uploadNoRe-host each result on the WebCake CDN and return cdn_url (default true — required for the image to show). Set false to only browse Pexels URLs.
per_pageNoHow many results (default 6)
orientationNoPreferred orientation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.31.8

TDQS

A4.6/5.0
Behavior5/5

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

Despite readOnlyHint=true already covering the safety profile, the description discloses substantial behavior: default re-hosting on the WebCake CDN, caching so repeats are free, the domain-whitelist rendering constraint, and the PEXELS_API_KEY environment requirement. This is exactly the auth/side-effect context annotations cannot express.

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-loaded with the purpose, then the critical rendering constraint, then defaults and the auth prerequisite. Dense but no filler; the uppercase IMPORTANT is slightly heavy-handed but serves a warning function.

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 carries the return-value burden well by naming cdn_url as the ready-to-use output and explaining caching. Combined with the auth prerequisite and the four documented params, an agent has everything needed to call it correctly.

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, but the description adds real meaning by tying the `upload` parameter to its consequence (re-hosting, ability to display) and introducing the returned `cdn_url` concept. It enriches the schema rather than repeating it.

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 ('Search stock photos (Pexels)') with the target context ('for a page/product'). It is clearly distinguishable from the nearest sibling, upload_images, which handles the user's own uploads rather than external stock search.

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?

Provides strong context: the CDN whitelisting constraint tells the agent when this tool matters and warns that raw Pexels URLs won't render. It implies usage for page/product imagery but never names an explicit alternative (e.g. upload_images) or a when-not-to-use case.

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