Skip to main content
Glama

fetch_asset

Download a single asset file (image, PDF, font, etc.) from its URL, save it to disk, and return file details as JSON. Ideal for fetching one specific file with its direct URL.

Instructions

Download a single asset file (image, PDF, font, CSS, any file) from its URL through the same unlock ladder as read_url, save it to disk, and return {path, content_type, bytes} as JSON. Use this for one specific file by its direct URL; to pull a whole page's assets at once use grab_site instead. Saves into out_dir when given, otherwise the current directory. Returns an 'Error: ...' string on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesDirect URL of the asset file to download.
out_dirNoDirectory to save into (optional; defaults to the current directory).
Behavior4/5

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

Discloses saving to disk, return format as JSON, and error string on failure. Mentions unlock ladder but no authorization details. No annotations present so description carries full burden; adequately transparent.

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?

Three sentences, each adding value. First sentence core purpose, second usage guidance, third parameter and error details. Front-loaded and no wasted words.

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?

Comprehensive for a simple download tool: explains return structure, error case, optional parameter, and relationship to siblings. No output schema but description suffices.

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 coverage is 100%, so baseline is 3. Description restates parameter meanings (direct URL, directory) but adds little beyond schema. Does not explain allowed file types or URL restrictions.

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?

Clearly states the tool downloads a single asset file, saves it to disk, and returns JSON. Specifies resource type (asset) and verb (download, save), and distinguishes from sibling grab_site.

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?

Explicitly says to use for one specific file by direct URL, and directs to grab_site for whole-page assets. Also references read_url for authentication context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/capad-xyz/searchts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server