Streamline MCP Server

Download multiple assets

download_multiple_assets

Read-onlyIdempotent

Use this when several icons are needed as files, with every hash from search_assets, in one call. Not for a single icon (download_asset). colors takes HEX codes or CSS named colors, not currentColor. Next: when building a project, fetch downloadUrl, unzip it and save the files there. Never link downloadUrl from project files: it expires. Export multiple icons (up to 50) as PNG or SVG, bundled into one .zip. Returns JSON with a single short-lived downloadUrl, expiresAt, expiresInSeconds, mimeType ("application/zip"), fileName, and the iconHashes it contains. All icons share the same render options. Give the user downloadUrl as a clickable link labelled with fileName, and tell them it expires in 2 hours; do not report a failure because you cannot fetch it yourself. Clients that can fetch files may GET downloadUrl directly (no API key needed) and unzip it. SVG-only params: responsive, strokeToFill.

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": {
      "format": "<format>",
      "iconHashes": "<iconHashes>",
      "size": "<size>"
    },
    "name": "download_multiple_assets"
  }
}

Input Schema

Name	Required	Description	Default
`size`	Yes	Image size in pixels (square).
`colors`	No	Array of HEX codes or CSS named colors.
`format`	Yes	Export format: "png" or "svg".
`iconHashes`	Yes	Icon IDs (hashes) from `search_assets` results, one per array element (max 50).
`responsive`	No	SVG only. Scales with container (viewBox, no fixed size).
`strokeWidth`	No	Thickness of vector paths.
`strokeToFill`	No	SVG only. Convert strokes to fills (strokeWidth ignored).
`backgroundColor`	No	Background color (default: transparent).	#ffffff00

Output Schema

Name	Required	Description	Default
`fileName`	Yes
`mimeType`	Yes
`expiresAt`	Yes
`iconHashes`	Yes
`downloadUrl`	Yes
`expiresInSeconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations: discloses that the URL expires in 2 hours, that GET requires no API key, and that the agent should not treat its own inability to fetch the file as a failure. This is exactly the kind of operational context annotations cannot carry. Slightly short of 5 only because file-size or zip-contents edge cases are left to the schema/output.

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 use case and the exclusion, then moves to constraints and return handling. Dense and mostly earns its words, though the run of imperative instructions about links and expiry is slightly longer than strictly needed.

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?

For an 8-parameter export tool with an output schema, the description covers invocation, shared-render semantics, the returned fields, and how to hand the result to the user. Nothing an agent needs to call it correctly and present the result is missing.

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 baseline is 3, but the description adds real constraints the schema lacks: `colors` accepts HEX or CSS named colors but not `currentColor`, all icons share the same render options, and the 50-icon cap is reinforced. It does not explain strokeWidth or backgroundColor behavior, so not a 5.

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 (export several icons as PNG/SVG bundled into one .zip) and immediately scopes it against the sibling: 'Not for a single icon (`download_asset`)'. An agent can distinguish this from download_asset without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('when several icons are needed as files'), explicit when-not ('Not for a single icon'), names the alternative, and prescribes the follow-up workflow (fetch downloadUrl, unzip, save files). It also warns against linking downloadUrl in project files.

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

All Streamline MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.