Skip to main content
Glama

get-assets

Retrieve and filter project assets or public content using criteria like type, date, author, or privacy settings to organize and access media files.

Instructions

List assets of a project team, or list all public assets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatedBeforeNoFilter results to only return assets updated before the specified ISO string date (exclusive). Requires the sortBy parameter to be "updatedAt"
sortDirectionNoSort results in ascending (asc) or descending (desc) order
privacyNoFilters result by asset privacy. If set to public, it will return -all- public assets from all organizations
inferenceIdNoList assets generated from a specific inference
modelIdNoList assets generated from all inferences coming from a specific model (this is not the training images)
updatedAfterNoFilter results to only return assets updated after the specified ISO string date (exclusive). Requires the sortBy parameter to be "updatedAt"
parentAssetIdNoList all the children assets that were generated from a specific parent asset
createdBeforeNoFilter results to only return assets created before the specified ISO string date (exclusive). Requires the sortBy parameter to be "createdAt"
sortByNoSort results by the createdAt or updatedAt
createdAfterNoFilter results to only return assets created after the specified ISO string date (exclusive). Requires the sortBy parameter to be "createdAt"
authorIdNoList assets generated by a specific author (the user that created the asset)
originalAssetsNoIf set to true, returns the original asset without transformation
pageSizeNoThe number of items to return in the response. The default value is 50, maximum value is 100, minimum value is 1
rootAssetIdNoList all the children assets that were generated from a specific root asset
typeNoList all the assets of a specific type. The parameter "type" and "types" cannot be used together. Can be any of the following values: inference-txt2img, inference-txt2img-ip-adapter, inference-txt2img-texture, inference-img2img, inference-img2img-ip-adapter, inference-img2img-texture, inference-inpaint, inference-inpaint-ip-adapter, inference-reference, inference-reference-texture, inference-controlnet, inference-controlnet-ip-adapter, inference-controlnet-img2img, inference-controlnet-reference, inference-controlnet-inpaint, inference-controlnet-inpaint-ip-adapter, inference-controlnet-texture, background-removal, canvas, canvas-export, canvas-drawing, detection, patch, pixelization, upscale, upscale-texture, upscale-skybox, vectorization, segment, segmentation-image, segmentation-mask, skybox-base-360, skybox-hdri, skybox-3d, restyle, reframe, generative-fill, texture, texture-height, texture-normal, texture-smoothness, texture-metallic, texture-edge, texture-ao, texture-albedo, image-prompt-editing, unknown, img23d, txt23d, 3d23d, 3d23d-texture, img2video, txt2audio, audio2audio, video2video, txt2img, img2img, txt2video, uploaded, uploaded-video, uploaded-audio, uploaded-3d, uploaded-avatar, upscale-video, assets with a type starting with "inference-" will be returned
paginationTokenNoA token you received in a previous request to query the next page of items
tagsNoList of tags, comma separated. Only for public assets on all teams.
typesNo
collectionIdNo
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions listing assets but doesn't disclose behavioral traits like pagination (implied by 'paginationToken' parameter), rate limits, authentication requirements, or whether it's read-only (implied by 'get' but not stated). The description adds minimal context beyond the tool name.

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 a single, efficient sentence with zero waste. It's front-loaded with the core purpose and includes two key scopes. Every word earns its place without redundancy or fluff.

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

Completeness2/5

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

Given the complexity (19 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the tool's behavior (e.g., pagination, default sorting), return format, error conditions, or how parameters like 'privacy' and 'collectionId' affect results. For a flexible listing tool with many filters, more context is needed.

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 description coverage is 89% (high), so the baseline is 3. The description adds no parameter-specific information beyond what's in the schema—it doesn't explain how parameters interact (e.g., 'privacy' affecting scope) or provide examples. The schema already documents most parameters well, so the description doesn't compensate but doesn't need to heavily.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('assets'), specifying two scopes: 'of a project team' and 'all public assets'. It distinguishes from some siblings like 'get-assets-by-asset-id' (single asset) and 'get-public-assets' (public-only), but doesn't explicitly differentiate from 'post-search-assets' or other listing tools.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description mentions two scopes but doesn't clarify prerequisites (e.g., team membership for project assets) or compare to siblings like 'get-public-assets' (which might overlap) or 'post-search-assets' (which might offer different filtering).

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/pasie15/scenario.com-mcp-server'

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