Midjourney MCP Server and API by Cotlet

Search creations in Midjourney

midjourney_search_creations

Read-onlyIdempotent

Search creations in the user's own Midjourney account from ChatGPT, Claude or any AI agent. Returns how to do it in Midjourney step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Midjourney Cloud Browser. Midjourney's official API: Midjourney has no public API (checked 5 Nov 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "midjourney_search_creations"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the crucial non-obvious trait that it "opens nothing by itself" and instead returns UI navigation steps (screens, buttons, fields). That is genuine value the annotations cannot convey. It still omits the exact shape and granularity of the returned instructions.

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 core constraint (returns instructions, opens nothing) is front-loaded, but phrases like "from ChatGPT, Claude or any AI agent" add no decision-relevant information, and the trailing "Midjourney's official API: Midjourney has no public API (checked 5 Nov 2026)" is awkwardly worded and redundant.

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?

For a zero-parameter, no-output-schema instructional tool, the description covers what it returns and what the agent should do afterward, which is the essential context. It could additionally note whether the steps vary by task or account, but nothing needed to invoke it correctly is missing.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. Nothing in the description misleads about inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ("Search creations in the user's own Midjourney account") and scopes it to the caller's own account. It does not compare against the other midjourney_* siblings, so the agent must infer that this is the discovery/instruction tool rather than one that actually performs a search.

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 workflow is stated implicitly: this tool returns step-by-step guidance, then "do it with the cotlet_browser_* tools in the user's Midjourney Cloud Browser." That tells the agent what comes next, but there is no explicit when-not-to-use guidance and no comparison to cotlet_app_guide, which appears to serve a similar instructional role.

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

All Midjourney MCP Server and API by Cotlet tools Inspect

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

Need Help?