Skip to main content
Glama

extract_assets

Extract images, sounds, fonts, and other non-code assets from SWF files. Specify asset types to extract, with output saved to a chosen directory.

Instructions

Extract images, sounds, fonts, and other assets from a SWF file.

This tool extracts non-code assets from a SWF file, including images, sounds, fonts, shapes, movie clips, and binary data.

Args: swf_path: Absolute path to the SWF file output_dir: Directory where extracted assets will be saved asset_types: Optional list of asset types to extract. Valid types: 'image', 'sound', 'font', 'shape', 'movie', 'binaryData', 'all' (default: ['all']) timeout: Optional timeout in seconds (default: 60)

Returns: Dictionary with: - success: Whether extraction succeeded - swf_path: Input SWF file path - output_dir: Output directory path - asset_types: List of asset types extracted - extracted_count: Number of assets extracted - message: Success message

Example: >>> extract_assets("/path/to/game.swf", "/path/to/output", asset_types=["image", "sound"]) { "success": true, "swf_path": "/path/to/game.swf", "output_dir": "/path/to/output", "asset_types": ["image", "sound"], "extracted_count": 127, "message": "Successfully extracted 127 assets" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
swf_pathYes
output_dirYes
asset_typesNo
timeoutNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations provided, the description must fully disclose behavior. It mentions extraction and returns a dictionary, but fails to state whether the operation is read-only, what happens on failure, or prerequisites (e.g., file existence). It does not disclose potential side effects or error conditions.

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?

The description is well-structured with a one-line summary, detailed Args/Returns, and an example. It is slightly verbose due to duplicating information that could be in the output schema, but the front-loading of the main purpose is effective.

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

Completeness3/5

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

The description covers the core functionality, inputs, and outputs, including an example. However, it lacks details on error handling, timeout behavior, and prerequisites. The default inconsistency also indicates incomplete specification.

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 adds meaning to the schema, explaining swf_path, output_dir, asset_types (with valid values), and timeout. However, it contradicts the schema defaults: description says asset_types default ['all'] and timeout default 60, while schema shows null defaults. This inconsistency undermines clarity.

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 verb 'Extract' and the resource 'assets from a SWF file', specifying asset types (images, sounds, fonts, etc.). It distinguishes itself from sibling tools like extract_actionscript (code) and decompile_swf (full decompilation), making its purpose immediately clear.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool over alternatives. While it implies it is for non-code assets, it lacks guidance like 'Use this when you need assets only, not code.' The sibling tool names provide context, but the description itself falls short of clear usage boundaries.

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/sublimnl/ffdecmcp'

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