Skip to main content
Glama
Sign In

MagicPixel

by art.magicpixel
OverviewDiscussionsAdmin

List marketplace assets

list_marketplace_assets
Read-onlyIdempotent

Browse MagicPixel's ready-made asset library (the editor's Assets tab, free for subscribers). Returns id, name, description, dimensions, tags, preview_url, category, genre, listing_kind (single|pack), artboard_count, contents / artboard_names, matched_items (when search hits a pack item name), cell_count, is_animated, frame_count. Packs (listing_kind=pack) are multi-artboard item sets — one file with N artboards, not an animation. Filter by category / genre / listing_kind / size / is_animated / search. Size: min_size and max_size each require BOTH width and height in range — use min_size=64 + max_size=64 for exact 64×64. Paginate with offset + limit; sort newest|name. Next: get_marketplace_asset to preview one; the user opens or drags it from the editor's Assets tab. Search matches name, description, pack contents (artboard names), tags, category, genre. artboard_names lists artboards in order (length = artboard_count, capped at 256); contents is the distinct-name index. Placeholder descriptions are returned as null. Older listings may have null category until curated — omit category or use search. If no matches: broaden filters once, then fall back to generate_pixel_art with the same size the user/game uses.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_marketplace_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNonewest (default) or name (A–Z).
tagsNoOnly listings that include all of these style tags (exact strings).
genreNoOnly listings that include all of these genres (fantasy, sci_fi, …).
limitNoMax rows (default 25).
offsetNoRow offset for pagination (default 0).
searchNoCase-insensitive match on name, description, or pack contents (artboard/item names); also exact tag / category / genre when the term matches.
categoryNoAsset type: character, tileset, environment, ui, vfx, item, prop, icon, other.
max_sizeNoBoth width AND height must be <= this. min_size=N + max_size=N → exact N×N (e.g. 64 for 64×64 characters).
min_sizeNoBoth width AND height must be >= this (logical pixels). Pair with max_size for a band or exact size.
is_animatedNoIf true, only animated sheets; if false, only still assets (packs are not animated).
listing_kindNosingle = one sprite; pack = multi-artboard item set (separate sprites in one file).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: pagination defaults (25 rows), the 256 artboard cap, that contents is a distinct-name index, that matched_items appears on pack-item search hits, and that placeholder descriptions come back as null. Only the openWorldHint implication (results may change over time / listing catalog evolves) is left implicit, which keeps it from a 5.

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-loads purpose, then return fields, then filtering, then pagination, then next-step routing — a sensible order with no filler sentences. The return-field enumeration is long, but it is earning its place given there is no output schema.

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?

With 11 optional parameters, no output schema, and no annotation coverage of returns, this description supplies the missing pieces: the returned field set, pack vs single semantics, pagination behavior, and a documented empty-result path. An agent has everything needed to call this correctly and interpret the response.

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 operational meaning: size filters require BOTH width and height in range and the min_size=64 + max_size=64 idiom for an exact size, plus which fields search covers and the category-null workaround. These are practical clarifications beyond the schema text rather than restatements.

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?

Opens with a specific verb and resource ("Browse MagicPixel's ready-made asset library") and pins the exact UI location (editor's Assets tab). It explicitly distinguishes packs from singles and animations, so an agent can differentiate this from generate_pixel_art and get_marketplace_asset without opening any 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?

Gives an explicit next step ("Next: get_marketplace_asset to preview one"), names the fallback when nothing matches (generate_pixel_art with the same size), and specifies a retry discipline ("broaden filters once"). It also states the exclusion case for is_animated ("packs are not animated") and how to work around uncurated null categories.

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

All MagicPixel toolsInspect
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.

Resources