Skip to main content
Glama

List image, video, speech and 3D models and prices

list_media_models
Read-onlyIdempotent

Every media model on Unrestrictable with its id, kind, endpoint, unit and price per image, second, generation or minute at each setting, next to the developer's price where recorded. No key needed. Live from GET /v1/catalog/media.

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_media_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly models of this kind.
searchNoA substring of the model id or name (nano-banana, veo, kling...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it provides critical behavioral traits such as the operational context ('Live from GET /v1/catalog/media') and access requirements ('No key needed'). This level of detail is highly valuable for an agent making runtime decisions.

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 exceptionally dense, efficiently packing the full list of returned data fields, the scope of the data, and the technical operational method into a single, highly readable paragraph without waste.

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?

Given that it is a read-only listing tool, it is perfectly complete. It details exactly what data structure to expect (ID, endpoint, pricing per unit) and the constraints of its operation, leaving no ambiguity for the agent.

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?

The description explains the intended function of both parameters: `kind` narrows the type, and `search` allows searching by ID or name, even providing concrete string examples like 'nano-banana'. This greatly enhances schema understanding.

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 purpose is extremely clear: listing specific media models (image, video, etc.) and detailing all associated financial and technical data like endpoint, unit pricing, and kind. It is precise and highly differentiated from generic list functions.

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

Usage Guidelines4/5

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

The description clarifies the scope (all models on Unrestrictable) and the specific data included, which strongly implies when to use it for pricing vs. other listing tools. It provides clear functional context, though it does not explicitly reference any sibling tool for comparison.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.