Skip to main content
Glama
Sign In
stock-images-mcp

stock-images-mcp

by jeanpfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

download_image

Save a Pexels, Unsplash, or Pixabay image to the download folder from its URL, with optional subfolder and filename; existing files are not overwritten.

Instructions

Download a stock image (https URL on pexels.com, unsplash.com or pixabay.com) into the download directory. Refuses to overwrite existing files.

Input Schema

NameRequiredDescriptionDefault
urlYesURL of the image to download
folderNoSubfolder inside the download directory
filenameNoOutput filename (auto-generated if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.1
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / folder / default
      Removed value: -"./downloads"
    • changedInput schema / properties / folder / description
      Previous value: -"Destination folder (default: ./downloads)"New value: +"Subfolder inside the download directory"
    • addedInput schema / properties / url / format
      Added value: +"uri"
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: files land in the download directory, only specific stock domains are accepted, and existing files are never overwritten (a refusal outcome). It omits auth requirements, failure modes for disallowed URLs, and rate limits, but the overwrite rule is genuinely useful beyond structured data.

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?

Two tight sentences with the resource, domain scope, destination, and overwrite rule front-loaded; every clause earns its place.

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 3-param download tool with no annotations and no output schema, the description covers destination and the non-overwrite guarantee, which is what an agent needs to avoid surprising behavior. Return-value and error semantics are left implicit, a minor gap.

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?

Schema description coverage is 100% and all three parameters are documented in the schema, so the baseline is 3. The description confirms the download directory as the destination, contextualizing folder/filename, but adds no syntax or format detail beyond the schema.

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

Purpose4/5

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

States a specific verb and resource ('Download a stock image') and constrains the accepted sources (pexels.com, unsplash.com, pixabay.com), which cleanly separates it from the search_images sibling. It stops short of explicitly naming or contrasting against that sibling, but the action is unambiguous.

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 statement of when to use this tool versus search_images or any alternative, and no prerequisites. The accepted-domain list is a constraint rather than usage guidance, so the agent must infer the search-then-download workflow.

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