ai-content-drop

List models

list_models

Read-onlyIdempotent

See which AI video or image models can make a video ad, animate a photo, produce a product clip or generate an image, with the credit cost of one generation. No account needed. The list is live; count is the number of models currently offered.

Input Schema

Name	Required	Description	Default
`type`	No	Model family to list. Defaults to video.
`max_credits`	No	Only return models costing this many credits or fewer.

Output Schema

Name	Required	Description
`note`	No
`type`	Yes
`count`	Yes	Models returned after filtering.
`models`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

changedOutput schema / properties / models / items / properties / credits / description

Previous value: -"Flat cost per generation."New value: +"Cost of one generation at the model's default settings; estimate_credit_cost quotes other lengths."

addedOutput schema / properties / models / items / properties / needs_start_image

Added value: +{
+  "description": "True when the model only animates an image: pass image_url to generate_video.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 1, 2026
- addedInput schema / required
```
Added value: +[]
```
First observedSep 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description needn't re-state safety. It adds genuine context beyond that: no authentication is required, the list is live rather than cached, and the `count` field reflects how many models are currently offered — useful traits an agent can't get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two front-loaded sentences with no filler; the capability list and cost note come first, then the operational caveats. The trailing `count` clause is slightly orphaned without saying what field it lives in, but nothing is wasted.

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

Completeness4/5

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

An output schema exists, so return structure needn't be explained, and the description covers the two things an agent can't infer: no auth required and live data. With zero required parameters and full schema coverage, this is close to complete; only the absence of an explicit 'use before generate_*' nudge keeps it from a 5.

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 coverage is 100% and both parameters are documented in-schema, including the type enum and its video default. The description gestures at credit cost (mapping loosely to max_credits) but adds no filtering syntax or semantics beyond what the schema already says, so baseline 3 applies.

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?

A specific verb-plus-resource ('see which AI video or image models...') with concrete capabilities enumerated (video ad, animate a photo, product clip, image) and the added dimension of credit cost per generation. It clearly distinguishes itself from generation siblings like generate_video, though it never explicitly contrasts with other list_* siblings such as list_ad_formats.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the discovery/cost-check step before calling a generation tool, and 'No account needed' hints at pre-auth contexts. But there is no explicit 'call this before generate_video to pick a model' or any condition excluding alternatives.

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

All ai-content-drop tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.