Skip to main content
Glama

create_mural

Create a new mural in a specified room, with options for title, dimensions, background color, and infinite canvas.

Instructions

Create a new mural in a room.

Args:
    room_id: The room ID to create the mural in (required).
    title: Title of the mural.
    background_color: Background color in hex with alpha (e.g. "#FFFFFFFF").
    width: Width of the mural in px (3000-60000, default 9216).
    height: Height of the mural in px (3000-60000, default 6237).
    infinite: If true, canvas is borderless and grows as you add widgets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
widthNo
heightNo
room_idYes
infiniteNo
background_colorNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose parameter behavior, such as the infinite canvas behavior ('grows as you add widgets') and background color format, but it does not mention side effects, permissions, or that this is a mutation beyond the verb 'create.' Some behavioral ambiguity remains.

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 description is compact and well-structured: a one-sentence purpose followed by a clean list of parameters. Every line conveys necessary information without unnecessary prose.

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?

The description covers all parameters and key behavioral traits, making it usable for a create operation. Although it omits usage alternatives and return value details, the output schema exists and the tool complexity is relatively low. It is nearly complete but could be slightly richer with usage context.

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?

The description enriches every schema parameter with meaningful details: ranges (3000-60000), defaults (9216/6237), requiredness (room_id), and the semantic interpretation of infinite. Since schema description coverage is 0%, this is essential and highly effective.

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 description opens with 'Create a new mural in a room,' which clearly identifies the action and resource. This distinguishes it from sibling tools like list_murals_in_room or the widget-creation tools (e.g., create_sticky_notes).

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. It simply states the creation action without discussing trade-offs or prerequisites beyond the required room_id.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alymohamedhassan/mural-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server