Skip to main content
Glama
playcanvas

PlayCanvas Editor MCP Server

Official
by playcanvas
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

list_assets

Read-only

Retrieve assets from a PlayCanvas project using filters for type, name, or tag. Paginated responses provide compact summaries; use full mode for complete asset JSON when needed.

Instructions

List project assets, returning compact summaries by default (id, name, type, folder, tags). Results are paginated: use limit (default 50) and offset; the response meta includes total, count, hasMore and nextCursor. Filter with type, name (case-insensitive contains) and/or tag. Use full=true only when you need the complete asset JSON (large). An empty result is a successful, empty list (not an error). When NOT to use: to search the public asset store (use store_search).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter by tag
fullNoReturn full asset JSON instead of the compact summary (much larger)
nameNoFilter by name (case-insensitive contains)
typeNoFilter by asset type
limitNoMax assets to return (default 50)
offsetNoNumber of assets to skip (use nextCursor from a previous page)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changedv0.7.0
    • addedInput schema / properties / full
      Added value: +{
+  "description": "Return full asset JSON instead of the compact summary (much larger)",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max assets to return (default 50)",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Filter by name (case-insensitive contains)",
+  "type": "string"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Number of assets to skip (use nextCursor from a previous page)",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "Filter by tag",
+  "type": "string"
+}
    • changedInput schema / properties / type / description
      Previous value: -"The type of assets to list. If not specified, all assets will be listed."New value: +"Filter by asset type"
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "css",
-  "cubemap",
-  "folder",
-  "font",
-  "html",
-  "json",
-  "material",
-  "render",
-  "script",
-  "shader",
-  "template",
-  "text",
-  "texture"
-]New value: +[
+  "animation",
+  "animstategraph",
+  "audio",
+  "binary",
+  "bundle",
+  "container",
+  "css",
+  "cubemap",
+  "folder",
+  "font",
+  "gsplat",
+  "html",
+  "json",
+  "material",
+  "model",
+  "render",
+  "scene",
+  "script",
+  "shader",
+  "sprite",
+  "template",
+  "text",
+  "texture",
+  "textureatlas",
+  "wasm"
+]
  2. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already provide readOnlyHint=true, and the description adds meaningful behavioral detail: pagination semantics (limit/offset, nextCursor, meta fields), default compact vs full payloads, and the fact that an empty result is a success, not an error. This is exactly the kind of nuance an agent needs and cannot get from schema or annotations.

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 front-loaded with the core purpose, then layers pagination, filtering, the full flag, empty-list behavior, and the sibling alternative without wasted words. Every sentence earns its place.

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 a list tool with no output schema, the description covers the return contract (compact fields, meta fields), pagination mechanics, filter semantics, performance consideration for full=true, and error semantics for empty results. An agent has enough to call it correctly without guessing.

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 the baseline is 3, but the description adds value beyond the schema by explaining how parameters work together (default limit of 50, offset used with nextCursor, filters combinable by type/name/tag) and when full is worth the size cost.

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 names a specific verb and resource ('List project assets') and immediately defines the default return shape (compact summaries with id, name, type, folder, tags). It also distinguishes itself from the public asset search by explicitly pointing to store_search, which makes it easy to tell apart from sibling tools.

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?

'When NOT to use: to search the public asset store (use store_search)' is an explicit routing rule to the correct sibling. It also states when full=true is appropriate, giving the agent actionable selection criteria beyond the raw schema.

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/playcanvas/editor-mcp-server'

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