Skip to main content
Glama

get-public-assets

List and filter public AI-generated assets from Scenario.com by date, type, model, tags, and other criteria to find specific creative resources.

Instructions

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
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"
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"
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
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.
typesNoList of the asset types to request. 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
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List all public assets' implies a read-only operation, but it doesn't specify whether this is a safe, non-destructive action, mention pagination behavior (implied by parameters like 'pageSize' and 'paginationToken'), rate limits, or authentication needs. The description is too vague to inform the agent adequately about how the tool behaves.

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 extremely concise with a single sentence, 'List all public assets', which is front-loaded and wastes no words. It directly states the tool's action without unnecessary elaboration, making it efficient for quick comprehension.

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 (13 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what 'public assets' are, how results are structured, or behavioral aspects like pagination. While the schema covers parameters well, the description fails to provide necessary context for effective tool use, especially for a list operation with many filtering options.

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 input schema has 100% description coverage, detailing all 13 parameters with clear explanations, enums, and constraints. The description adds no additional parameter information beyond the schema, so it doesn't enhance understanding. According to the rules, with high schema coverage (>80%), the baseline score is 3, as the schema does the heavy lifting.

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

Purpose3/5

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

The description 'List all public assets' clearly states the verb ('List') and resource ('public assets'), making the purpose understandable. However, it lacks specificity about what 'public assets' are in this context (e.g., media files, models, etc.) and doesn't distinguish it from sibling tools like 'get-assets' or 'get-public-assets-by-asset-id', which offer different scopes or functionalities.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, such as authentication requirements, or compare it to sibling tools like 'get-assets' (which might list private assets) or 'get-public-assets-by-asset-id' (for a single asset). This leaves the agent without context for tool selection.

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