stock-image-mcp

Overview Schema Source Related Servers Discussions Admin

download_image

Downloads an image URL to a local file path, enabling direct embedding in blog post assets. Returns the saved path and attribution text if available.

Instructions

Download an image URL to a local path so it can be embedded directly in a blog post's asset folder. Returns the saved path and, if the image was previously returned by a search call, its attribution text.

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": {
      "url": "<url>",
      "dest_path": "<dest_path>"
    },
    "name": "download_image"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`provider`	No
`dest_path`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jul 31, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the return value (saved path and optional attribution text) and the condition for attribution, but it omits details about file overwrites, error handling, or network requirements.

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 two sentences, front-loaded with the action, and every sentence adds value. There is no redundant or excessive wording.

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 simple download tool with an output schema, the description covers the core purpose, usage context, and return behavior. It omits edge cases and provider semantics, but the essential guidance is complete enough for basic invocation.

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 description explains url and dest_path implicitly through the action and return value, but the provider parameter is not described, leaving its role unclear. With 0% schema coverage, this is only partial compensation for the gap.

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 clearly states the tool downloads an image URL to a local path for embedding in a blog post's asset folder. It uses a specific verb and resource, and distinguishes itself from sibling search/attribution tools by focusing on the download action.

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?

The description implies when to use the tool—when you have an image URL and need a local copy—and provides context about the asset folder. It does not explicitly mention alternatives or when not to use it, but the purpose is clear enough relative to siblings.

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

Deploy Server