Skip to main content
Glama
Sign In

Meta Muse MCP Server by useapi.net (third-party)

by net.useapi
OverviewDiscussionsAdmin

Generate an image

muse_generate_image

Make one image with Muse (Meta's AI agent) from a prompt, optionally editing or combining up to 9 input images (image_1..image_9 as asset ids; name them image_1, image_2… in the prompt, and say the aspect ratio in the prompt). Waits up to ~50 s: returns the finished image (assetId, download url, a preview) or, if still running, the jobid to pick up with muse_get_job. Uses the account's weekly Muse allowance. POST /jobs/image.

Input Schema

NameRequiredDescriptionDefault
emailNoThe Muse account to run on. When omitted, the account that holds the inputs, or a healthy account with allowance left.
promptYesWhat to make, up to 5000 characters. Name the inputs image_1, image_2… and say the aspect ratio.
image_1NoInput image 1: an asset id from muse_upload_asset, muse_list_assets, a job result or a chat file. Name it image_1 in the prompt.
image_2NoInput image 2: an asset id from muse_upload_asset, muse_list_assets, a job result or a chat file. Name it image_2 in the prompt.
image_3NoInput image 3: an asset id from muse_upload_asset, muse_list_assets, a job result or a chat file. Name it image_3 in the prompt.
image_4NoInput image 4: an asset id from muse_upload_asset, muse_list_assets, a job result or a chat file. Name it image_4 in the prompt.
image_5NoInput image 5: an asset id from muse_upload_asset, muse_list_assets, a job result or a chat file. Name it image_5 in the prompt.
image_6NoInput image 6: an asset id from muse_upload_asset, muse_list_assets, a job result or a chat file. Name it image_6 in the prompt.
image_7NoInput image 7: an asset id from muse_upload_asset, muse_list_assets, a job result or a chat file. Name it image_7 in the prompt.
image_8NoInput image 8: an asset id from muse_upload_asset, muse_list_assets, a job result or a chat file. Name it image_8 in the prompt.
image_9NoInput image 9: an asset id from muse_upload_asset, muse_list_assets, a job result or a chat file. Name it image_9 in the prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / replyRef
      Removed value: -{
-  "description": "Optional reference echoed back in the job record.",
-  "maxLength": 1024,
-  "type": "string"
-}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false (mutation), openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds key behavioral context: it waits up to ~50 seconds, returns either the finished image or a jobid to poll, uses the account's weekly allowance, and the endpoint. This goes beyond annotations by detailing timeout and return behavior.

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 a single, dense sentence that front-loads the core action and then details optional inputs and return behavior. It is efficient but slightly packed; still, every part earns its place.

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?

Given 11 parameters with full schema coverage and no output schema, the description provides necessary context: input handling, timeout, return values, and allowance usage. It is complete enough for an agent to call correctly, though it could mention error handling or rate limits.

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 parameters thoroughly. The description adds some usage detail (naming images in the prompt, specifying aspect ratio) but does not add significant new meaning beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Make one image with Muse') and distinguishes itself from the sibling muse_generate_video by naming the resource type. It also clarifies scope by noting optional editing/combining of up to 9 input images.

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?

Explains when to use it (to generate an image from a prompt) and how to use inputs, but does not explicitly state when to use alternatives like muse_generate_video or when not to use this tool (e.g., for simple asset retrieval). It provides clear context but lacks exclusions.

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

All Meta Muse MCP Server by useapi.net (third-party) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources