Skip to main content
Glama

Midjourney Import

lab_umzug

Bring Midjourney exports into a project (FilmLab calls this 'Umzug'). Midjourney has no API, so the person downloads their images or ZIP and this tool carries them on. Give EXACTLY ONE of: dateien (names/types/sizes of local files → signed PUT addresses with a ready curl line; PUT the raw bytes, then call again with quellen from weiter), quellen (after the PUT: starts the import job → job_id; poll lab_get_job — result.bildzeilen lists image_id and datei per image (the prompt per image comes with bilder: true), result.gesperrt names refused images with the reason, result.ungeprueft images whose check was unreachable), prompts (pasted Midjourney prompts, one per line → parameters split and what does not carry over, e.g. --sref codes; free, no job), anker ({name, image_ids ≤ 12} → a look anchor for lab_generate's anker_id; images of real people are refused) or bilder: true (the project's imported images with image_id and prompt). Every imported image is declared AI material (EU AI Act Art. 50) — no herkunft question. An image_id works directly in lab_animate (source_image_id), as a seed in lab_generate and in lab_referenz_aus_bild. Uploading is free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ankerNoBuild a look anchor from imported images
bilderNotrue: list the project's imported images
dateienNoLocal files to upload: ZIP archives or single PNG/JPG/WEBP
promptsNoPasted Midjourney prompts, one per line
quellenNoAfter the PUT: exactly the `quellen` from the previous answer's weiter.argumente
project_idYesProject id (from lab_list_projects) — positive integer as string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnly=false/destructive=false, so the description carries the real burden and delivers: uploading is free, prompts cost no job, real-person images and look-anchor images are refused, and every imported image is declared AI material under EU AI Act Art. 50 with no herkunft prompt.

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-loaded with the purpose, then a single dense paragraph enumerating modes in workflow order; every clause carries operative information (cost, refusals, handoffs). It is long and parenthetical-heavy, but not padded — slightly harder to scan than optimal for a polymorphic tool.

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?

Despite no output schema, the description documents return semantics (job_id, result.bildzeilen/gesperrt/ungeprueft, weiter), the polling target, and downstream handoffs, so an agent has everything needed to drive the multi-step import.

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

Parameters5/5

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

Schema coverage is 100% (baseline 3), but the description adds semantics the schema cannot express: the sequence dependency of quellen on the previous 'weiter' payload, the ≤12 image_ids cap for anker, and per-mode output behavior (job_id, weiter, result fields). This exceeds the structured data meaningfully.

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+resource ('Bring Midjourney exports into a project') and maps the internal alias 'Umzug'. An agent can distinguish this from sibling import/media tools without opening the schema.

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?

Explicitly names the five mutually exclusive modes (dateien, quellen, prompts, anker, bilder) and the 'EXACTLY ONE of' rule, spells out the ordered workflow (dateien → PUT → quellen → poll lab_get_job), and points to the sibling tools where an image_id is consumed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources