Skip to main content
Glama
jau123

MeiGen AI Image Generation MCP

by jau123

generate_marketing_poster

Design a promotional poster for a brand, event, or topic. Provide subject and optional copy or images; the service plans the layout and generates the poster.

Instructions

Design one poster for a brand, shop, event, promotion or topic. Required: only the subject. An image is not required. Exact wording, dates, offers, logo, product photos and style references are optional. Keep supplied copy with autoCopy=false; never invent event details or offers. The service plans the layout and writes the prompt. Requires a MeiGen API key configured for this local npm server (MEIGEN_API_TOKEN or saved local configuration), and purchased credits only. Local files and external public HTTPS URLs are uploaded automatically. Use the dedicated skill directly; skip unrequested prompt enhancement, preference loading and delegation. Preserve caller-supplied inputs. Infer omitted optional settings from the request and defaults; when only a requested count is known, choose suitable modules unless the caller selected them. Ask only for missing required material or unresolved scope. An explicit user request or authorized upstream workflow establishes its count, quality and budget: do not reconfirm that scope or add paid images. The caller persists a requestId for each logical step; never ask an end user for technical IDs. Use live list_skills prices and account for in-flight charges when planning within a budget; a batch is not atomic and an estimate is not a server-enforced spending cap. Recovery actions take precedence over generic retry advice: check an interrupted submission, preserve exact retryParameters and do not create a new ID or replace failed modules automatically. Retry a temporary upload at most once after the suggested wait. Return structured status, handles, errors and completed URLs to the caller; it owns progress, previews, downloads and final presentation. If interacting directly with the user, explain the problem and a concrete next step in their language. Describe image details only after actual inspection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
logoNoOptional exact brand logo to reproduce accurately, not a style reference. An accessible absolute local path (Windows drive/UNC, POSIX, ~/, or file://) or public direct HTTPS image URL without credentials, fragments or custom ports. Relative paths are ambiguous and rejected. Files are fully decoded, metadata removed, transparency preserved; GIF uses the first frame. Never invent attachment paths or URLs.
brandYesPoster subject: brand, event, shop, campaign or topic.
ratioNoSupported output ratio from list_skills for this Skill; omit for its default.
contentNoPoster brief when autoCopy=true; exact visible wording when autoCopy=false (the selected language may translate it). Put style, layout and design directions in extraNotes or customStyle, not in verbatim content.
qualityNolow=Fast (default); medium=Pro. These select rendering quality, not output resolution. Read list_skills for current output specifications and purchased-credit prices; no fixed completion time is guaranteed.
styleIdNoPreset ID, not its display label; choose from list_skills style options. Omit styleId and customStyle for Auto. Nonempty customStyle overrides this preset.
autoCopyNoDefault true: compose copy from the brief. False: use supplied wording faithfully; selected language may translate it.
languageNoCopy language, e.g. auto, en, zh; see list_skills for supported values
uiLocaleNoOptional UI locale fallback; language controls the text inside images.
requestIdYesGenerate a new UUID for a new paid request; reuse the SAME requestId and inputs on retry. Use check_skill after interruptions.
extraNotesNoAdditional verified facts, explicitly requested display copy, or layout/design constraints, up to 500 characters. Treat design instructions as directions, not text to print verbatim. Preserve supplied details; do not invent dates, prices, offers or claims.
styleImageNoOptional PRIMARY visual-style reference: palette, lighting, typography and mood. Do not copy its content, products, text or layout; written style is only a compatible supplement. An accessible absolute local path (Windows drive/UNC, POSIX, ~/, or file://) or public direct HTTPS image URL without credentials, fragments or custom ports. Relative paths are ambiguous and rejected. Files are fully decoded, metadata removed, transparency preserved; GIF uses the first frame. Never invent attachment paths or URLs.
customStyleNoOptional written visual direction, up to 200 characters. Nonempty text overrides styleId; omit both for Auto. If styleImage is supplied, supplement its visual style without conflicting with it.
productImagesNoOptional product/subject photos, up to three; these identify what the poster depicts, not its visual style.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.1

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses authentication/credit requirements, automatic file uploads, non-atomic batch behavior, retry semantics, budget estimation caveats, and the caller's ownership of progress and presentation. It also warns against inventing event details or describing images before actual inspection.

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?

The description is front-loaded with purpose and essential constraints, and the guidance is topically organized from scope to prerequisites to execution to recovery. However, it is a long single paragraph with some operational details that could be condensed or split for easier scanning, though virtually every sentence carries actionable information.

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?

For a complex tool with 14 parameters and no output schema, the description covers the full call lifecycle: prerequisites, file upload, budget planning, retry handling, caller responsibilities, and response shape. It also correctly points to list_skills for dynamic details like prices, ratios, and style options, leaving no critical gap for an agent to invoke the tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds meaningful semantic guidance beyond the schema by explaining copy preservation rules, omitted-setting inference, confirmation boundaries, and requestId reuse/retry behavior. It does not redefine every parameter, but it clarifies how parameter choices should be made in context.

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 opens with a specific verb and resource: 'Design one poster for a brand, shop, event, promotion or topic.' It clearly states the tool's unique scope (a single poster) and differentiates it from generic image generation by noting an image is not required and the service plans the layout and writes the prompt.

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 gives clear context: use the dedicated skill directly, skip prompt enhancement, preference loading and delegation, and ask only for missing required material. It does not explicitly name sibling alternatives like generate_image for non-poster requests, but it does define the tool's boundaries and prerequisites, including API key and purchased credits.

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