Skip to main content
Glama
Sign In
pexels-mcp-server

pexels-mcp-server

by garylab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

collections_featured

Retrieve a list of featured photo and video collections from Pexels.

Instructions

List featured collections

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "collections_featured"
  }
}

Input Schema

NameRequiredDescriptionDefault
per_pageNoResults per page (string, 1-80)15
pageNoPage number (string, minimum 1)1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior1/5

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

No annotations exist, so the description carries full burden. It discloses no behavioral traits such as read-only nature, side effects, or safety. The description is completely opaque about what 'list' entails (e.g., rate limits, auth, or data structure).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only 4 words, which is concise but under-specified. It restates the tool name without adding value, making it tautological rather than helpfully succinct.

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

Completeness2/5

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

Given 2 parameters, no output schema, and no annotations, the description fails to explain what 'featured collections' are, pagination behavior beyond schema, or how results are structured. It is minimally complete.

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?

The schema covers 100% of parameters with descriptions, so baseline is 3. The tool description adds no additional meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List featured collections' is clear in verb and resource, but it does not differentiate from siblings like 'collections_media'. The term 'featured' is implied by the name, so the description adds minimal new meaning.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'collections_media' or 'photos_curated'. There is no mention of context, prerequisites, or exclusion criteria.

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