Skip to main content
Glama

Pexels

by io.github.pipeworx-io

Featured Collections

featured_collections
Read-onlyIdempotent

List Pexels' featured curated collections; returns collection id, title, description, and media counts for photos and videos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoCurrent page number
per_pageNoNumber of results per page
next_pageNoURL for next page of results
collectionsNoArray of featured collection objects
total_resultsNoTotal number of results available

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changed
    • changedOutput schema / properties / collections / items / properties / description / type
      Previous value: -"string"New value: +[
+  "null",
+  "string"
+]
    • changedOutput schema / properties / collections / items / properties / media_count / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / collections / items / properties / photos_count / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / collections / items / properties / videos_count / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / page / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / per_page / type
      Previous value: -"integer"New value: +"number"
    • changedOutput schema / properties / total_results / type
      Previous value: -"integer"New value: +"number"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint: false, which cover safety. The description adds what the return contains (collection id, title, description, media counts), but does not disclose additional behavioral traits such as pagination, ordering, or potential rate limits. Since the bar is lower with strong annotations, this is adequate but not enriched.

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?

The description is a single, front-loaded sentence with a clear verb and essential return-value details. Every word contributes to understanding the tool's purpose and output.

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?

For a zero-parameter listing tool with a rich output schema and strong annotations, the description is largely complete. It explains what the tool returns, which is sufficient, though it could optionally mention that no pagination is needed or that all featured collections are returned at once. Minor gap, but not material.

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?

This tool has zero parameters, so the baseline is 4. The description correctly implies no inputs are needed and clarifies the output focus. There is no parameter-level information to add beyond the empty 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?

The description uses a specific verb ('List') and specifies the resource ('Pexels' featured curated collections'). It also clearly distinguishes itself from sibling tools like collection_media (which likely retrieves media within a collection) and photo/video search tools by stating it returns collection metadata.

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

Usage Guidelines3/5

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

The description implies usage: use this tool to list featured curated collections. However, it does not explicitly state when to prefer this over collection_media or search tools, nor does it mention any exclusions. Some context is present but guidance is minimal.

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

All Pexels toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

Many tools are clearly from distinct domains (Pexels media, Pipeworx data, Polymarket betting, utility), but within each domain there is significant overlap (e.g., ask_pipeworx vs ask_pipeworx_grounded vs deep_research, or numerous polymarket tools). Detailed descriptions help differentiate, but some tools could still be confused.

Naming Consistency3/5

Naming conventions vary: some tools use verb_noun (ask_pipeworx, compare_entities), others are single-word (photo, video), and some mix patterns (photo_curated vs photo_search). The Pexels subset is consistent, but the overall set includes tools from other ecosystems with different styles.

Tool Count2/5

With 38 tools, the set is bloated for a Pexels server. Only 8 tools are actually Pexels-related; the rest are Pipeworx data query, Polymarket betting, and utility tools. This mismatch makes the count inappropriate for the stated server purpose.

Completeness4/5

For the Pexels domain, the tool set covers search, fetch, and collections for both photos and videos, which is adequate. The unrelated tools add bloat but don't create gaps in the Pexels functionality. Minor missing features like uploads or editorial content are not critical.

Resources