MeiGen AI Design MCP

Overview Schema Source Related Servers Discussions Admin

list_models

Read-only

List available AI image generation models and their capabilities so you can find a model for SVG, GIF, or mask-based editing before generating images with the correct model ID and output format.

Instructions

List available AI image generation models and their capabilities. For a vector or SVG request, find the image model listing SVG; for an animated or looping GIF, find the image model listing GIF and read its per-size frame limits. Then use generate_image with that model ID and output format. For annotated still-image edits, check imageOutput.editing for imageMask/imageMarkup support, original-source requirements and limits; absent capabilities do not imply support. For up-to-date pricing, see https://www.meigen.ai/model-comparison.

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

Input Schema

Name	Required	Description	Default
`activeOnly`	No	Only show active models (default: true)

Output Schema

Name	Required	Description	Default
`error`	No
`models`	Yes
`success`	Yes
`configuredProviders`	Yes
`executionCapabilities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.1.0Oct 13, 2026
- changedOutput schema / properties / configuredProviders / items / enum
```
Previous value: -[
-  "meigen",
-  "openai",
-  "comfyui"
-]New value: +[
+  "meigen",
+  "openai"
+]
```

Changed1 schema field changedv2.0.1Sep 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "configuredProviders": {
+      "items": {
+        "enum": [
+          "meigen",
+          "openai",
+          "comfyui"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "error": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "retryable": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "code",
+        "message",
+        "retryable"
+      ],
+      "type": "object"
+    },
+    "executionCapabilities": {
+      "additionalProperties": false,
+      "properties": {
+        "concurrency": {
+          "type": "string"
+        },
+        "download": {
+          "type": "boolean"
+        },
+        "maxConcurrentSubmissions": {
+          "type": "number"
+        },
+        "submitOnly": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "submitOnly",
+        "download",
+        "maxConcurrentSubmissions",
+        "concurrency"
+      ],
+      "type": "object"
+    },
+    "models": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "models",
+    "configuredProviders",
+    "executionCapabilities"
+  ],
+  "type": "object"
+}

Addedv1.3.1May 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds meaningful interpretive context beyond that — that capability absence must not be read as support, that GIF frame limits are per-size, and that pricing lives externally at a URL. It does not disclose the effect of the activeOnly default (that inactive models are hidden) or anything about result ordering, so a small gap remains.

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?

Front-loads the core purpose in the first sentence, then chains three task-specific instructions in a logical order. It is dense but every clause carries actionable routing information; the only marginally expendable element is the external pricing pointer.

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 shape need not be described, and the description instead explains how to read the capability fields that matter for downstream calls. What is missing is the interaction between the default activeOnly filter and capability discovery, and no note on the size/scope of the listing.

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 sole parameter activeOnly is fully documented in the schema (100% coverage), so the baseline is 3. The description adds nothing about filtering behavior, which matters because a hidden inactive model could be mistaken for a nonexistent capability when the agent is hunting for SVG/GIF support.

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?

States a specific verb and resource ('List available AI image generation models and their capabilities') and implicitly separates itself from the generation siblings by naming generate_image as the follow-on step. An agent can immediately tell this is the discovery/lookup tool rather than a generation or editing tool.

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?

Gives concrete conditional guidance: use this listing to find an SVG-capable model, to find GIF models and read per-size frame limits, and to check imageOutput.editing for mask/markup support before requesting an annotated edit. It also names the next tool to call (generate_image with the chosen model ID and output format). It lacks explicit when-not-to-use framing, so it falls short of a 5.

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

Deploy Server