Skip to main content
Glama
Sign In
JensithAxboe

MeiGen AI Design MCP

by JensithAxboe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

generate_marketing_poster

DestructiveIdempotent

Designs a marketing poster for a brand, shop, event, promotion, or topic, planning the layout and writing the image prompt from a short brief.

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. This legacy local npm path requires an existing MeiGen key (MEIGEN_API_TOKEN or saved local configuration) and purchased credits. New connections use remote OAuth at https://www.meigen.ai/api/mcp. 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

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. auto infers from the poster brief; omit to keep default 4:5.
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. First observedv3.3.3

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructive=true and openWorld=true, but the description adds substantial context the agent could not infer: this legacy local path requires a MeiGen key (MEIGEN_API_TOKEN) and purchased credits, new connections use remote OAuth, local files and public HTTPS URLs are auto-uploaded, a batch is not atomic and an estimate is not a server-enforced cap, and interrupted submissions must be checked before retrying. It also discloses the output contract (structured status, handles, errors, URLs) despite there being no output schema.

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

Conciseness3/5

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

The key purpose and required-input line is correctly front-loaded, but the body runs long and a large fraction is family-wide operational boilerplate (caller persists progress and previews, explain problems in the user's language, describe image details only after inspection) that does not help select or invoke this specific tool. It earns its place functionally more than it does economically.

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?

With 14 parameters and no output schema, the description covers the gaps that matter: credential and credit prerequisites, upload path rules, idempotency via requestId reuse, failure recovery precedence over generic retry, non-atomic batching, and the shape of what comes back. An agent has enough to call it correctly and to handle partial failure without further documentation.

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 schema already carries per-parameter meaning and the baseline is 3. The description nonetheless adds cross-parameter semantics: copy must be kept with autoCopy=false, event details and offers must never be invented, optional settings are inferred from the request and defaults, and a count alone should drive module selection. It stops short of explaining much about ratio, language, or uiLocale beyond what the schema says.

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 opening sentence names a specific verb and artifact ('Design one poster') and bounds the subject domain (brand, shop, event, promotion, topic), then adds that the service plans the layout and writes the prompt. That distinguishes it from the generic image siblings such as generate_image or generate_ai_background, which produce raw imagery rather than a composed poster.

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

Usage Guidelines5/5

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

It explicitly routes away from sibling capabilities — 'Use the dedicated skill directly; skip unrequested prompt enhancement, preference loading and delegation' names enhance_prompt and manage_preferences as things NOT to call. It also states when to ask the user ('only for missing required material or unresolved scope') and when not to reconfirm scope, which is unusually precise routing guidance.

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