Mobbin

Create Collection

create_collection

Create a collection for the user's Mobbin MCP connection, and return its id and link. It starts empty: call save_content with the returned id to add screens, flows or sections. It is private: only the user and their teammates can open the link, and say so when you give it out. The user can make it public on mobbin.com. Use it when the user asks for a new collection, or wants to save into one that list_collections does not have. Collection names are not unique, so check list_collections first when the user may already have one with that name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description
`name`	Yes	The collection's title on Mobbin.
`description`	No	What the collection is for, shown under its name on Mobbin.
`task_intent`	No	One short sentence summarizing the user's overall task. Helps return more relevant results. Write it in English even when the conversation is in another language. MUST be the same across all calls for the same task. Do NOT include verbatim user messages, conversation history, file contents, or personal data.

Output Schema

Name	Required	Description
`id`	Yes	A collection id from list_collections, or "all-saved" for everything saved for the user's Mobbin MCP connection.
`name`	Yes	Not unique: check every entry for the same name before using one.
`is_public`	Yes	If true, anyone with the link can open it. If false, only the user and their teammates can open it. Always false for All saved.
`mobbin_url`	Yes	Link to open it on Mobbin.
`description`	Yes	Empty when the user wrote none.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only declare this is a non-read-only, non-destructive, closed-world mutation. The description goes well beyond: the collection starts empty, save_content must be called with the returned id to fill it, it is private to the user and teammates by default, can be made public on mobbin.com, and the agent is told to disclose the privacy when handing out the link.

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

Conciseness5/5

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

The purpose and return value come first, then the follow-up action, then the privacy constraint, then the usage routing — front-loaded in order of necessity. Each sentence carries distinct information; there is no restatement of the name or title.

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 mutation tool with an output schema, the description still covers what an agent must know to act: what gets created, what comes back, the required follow-up call, the visibility model, and how to avoid duplicate-named collections. Nothing material 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?

Schema coverage is 100%, so the baseline is 3. The description adds real semantics for the key `name` parameter by noting collection names are not unique and should be checked against prior collections — a constraint the schema does not express. `task_intent` is left to the schema.

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 and resource ("Create a collection") plus the side effect of returning its id and link. It also implicitly distinguishes itself from list_collections and save_content by naming both as different operations, so an agent can route correctly without opening any 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?

Explicit trigger conditions: "Use it when the user asks for a new collection, or wants to save into one that list_collections does not have." It also names the alternative (list_collections) and the precondition for checking it (names are not unique), which is exactly the when-to-use/when-to-check guidance the dimension rewards.

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

All Mobbin tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.