Skip to main content
Glama

list_models

Browse 550+ generative AI models by type and keyword to find model IDs for generation workflows.

Instructions

Browse the Pixio model catalog (550+ models) with optional filters.

Step 1 of the three-call contract for running any generation:

  1. list_models — find a model id (filter by type and/or query).

  2. get_model_params(model_id) — fetch that model's exact input schema.

  3. generate(model_id, params) — run the job.

Args: type: Exact model type to match, e.g. "text-to-image", "image-to-image", "image-to-video", "text-to-video", "video-to-video", "text-to-audio". query: Case-insensitive substring matched against each model's id, name, and description (e.g. "flux", "background removal"). limit: Maximum number of models to return; clamped to 1..200 (default 50). offset: Number of matching models to skip, for pagination (negative values are treated as 0).

Returns: {"models": [{"id", "name", "type", "credits", "company", "description"}, ...], "total_matching": , "returned": <len of "models">, "offset": }. "credits" is the catalog-listed cost per generation; descriptions are truncated to 200 characters. The catalog is cached for ~10 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
limitNo
queryNo
offsetNo
Behavior5/5

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

Discloses caching behavior (~10 minutes), truncation of descriptions to 200 characters, clamping on limit parameter, and handling of negative offset. Provides detailed return structure without contradicting any annotations (none provided).

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?

Well-structured: summary sentence, contract overview, bulleted Args, Returns section. Every sentence adds value without unnecessary verbosity. Ideal length for an AI agent.

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?

Comprehensive for a tool with 4 parameters, no output schema, and no annotations. Covers parameter constraints, return format, caching, and positions within the tool ecosystem (sibling tools). No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description thoroughly explains each parameter: type examples, query as case-insensitive substring matching with examples, limit clamped to 1-200 with default 50, offset with negative handling. Adds significant meaning beyond the bare schema.

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 tool browses the Pixio model catalog with optional filters. It identifies the resource and action, and distinguishes itself from siblings by being step 1 of a three-call contract.

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?

Explicitly describes the three-call contract for running generations, positioning list_models as the first step to find a model ID. Provides clear when-to-use guidance with alternatives (get_model_params and generate) listed.

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/RealDealCPA-VR/Pixio-MCP'

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