glm-image-mcp-server

generate_image

Generate images from text prompts, select HD or standard quality, and choose from preset aspect ratios or custom dimensions.

Instructions

Generate an image from a text prompt using Z.AI glm-image model

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "generate_image"
  }
}

Input Schema

Name	Required	Description
`prompt`	Yes	The text prompt describing the image to generate
`quality`	No	Image quality: "hd" (default) or "standard"
`custom_size`	No	Custom size (e.g., "1536x1024"). Must be 1024-2048px, divisible by 32, max 2^22 total pixels. Ignored if size_preset is specified
`size_preset`	No	Recommended size preset by aspect ratio. "1:1"=1280x1280 (default), "3:2"=1568x1056, "2:3"=1056x1568, "4:3"=1472x1088, "3:4"=1088x1472, "16:9"=1728x960, "9:16"=960x1728
`output_filename`	No	Optional output filename (without path)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 9, 2026

TDQS

B3.4/5.0

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. It only states the core action and model, with no mention of side effects (e.g., file savings, return format, rate limits, or asynchronous behavior). This leaves significant behavioral ambiguity.

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 a single, well-structured sentence that front-loads the essential verb and object. No unnecessary words or redundancy.

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?

Despite the schema covering all parameters, there is no output schema, and the description does not explain what the tool returns (e.g., file path, URL, base64) or any side effects like file saving. For a tool with 5 parameters and no return specification, the description should clarify the outcome, but it does not.

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 description coverage is 100%, so the schema already documents all five parameters. The description itself adds no additional parameter meaning beyond what the schema provides, matching the baseline.

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 action ('Generate'), the resource ('an image'), and the source ('from a text prompt using Z.AI glm-image model'). This is specific and leaves no ambiguity about what the tool does, even without sibling comparisons.

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?

The description implies usage for image generation from text, but provides no explicit guidance on when to use this tool versus alternatives, or any prerequisites. With no siblings listed, the implied usage is acceptable but not enhanced.

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

Deploy Server

Other Tools

generate_imageB