Skip to main content
Glama

create_shapes

Create shape widgets on a Mural by specifying position, shape type, text, and styling. Add one or more shapes to build diagrams and flowcharts.

Instructions

Create one or more shape widgets on a mural (limit 1000).

Each widget object supports:
  - x, y (required): Position in px.
  - shape (required): One of: ellipse, rectangle, rounded_square, rhombus_smart, triangle_smart,
    hexagon_smart, pentagon_smart, diamond, process, decision, terminator, start, end, delay,
    data, database, document, multiple_documents, predefined_process, manual_input, manual_loop,
    preparation, stored_data, connector, merge, or, summing_junction, display, direct_data,
    internal_storage, papertape, loop_limit, off_page_connector, cloud, cross, star, badge,
    ribbon, step, trapezoid, octagon, speech_bubble_left, speech_bubble_right, speech_bubble_center,
    thinking_bubble_left, thinking_bubble_right, arrow_right, arrow_left, arrow_down, arrow_top,
    arrow_left_right, brace_left, brace_right, note_left, note_right, teardrop_bubble, right_triangle.
  - text: Plain text content.
  - htmlText: HTML-formatted text.
  - width, height: Size in px (default 138).
  - style: { backgroundColor, borderColor, borderStyle, borderWidth, bold, italic, underline, strike, font, fontColor, fontSize, textAlign }.
  - parentId: ID of parent area widget.

Args:
    mural_id: The mural ID.
    widgets: Array of shape objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widgetsYes
mural_idYes

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 discloses useful behavioral details like the 1000-widget limit, required x/y coordinates, and default width/height, but doesn't mention authentication, error handling, partial success behavior, or side effects beyond creation. This is moderate transparency.

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 front-loaded with a clear one-line purpose, then uses structured bullets to detail widget properties. The long shape list is necessary and not padding; every sentence adds value. No fluff or repetition.

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 the essential parameters, defaults, limits, and style options for a creation tool. An output schema exists, so return values don't need explanation. Minor gaps remain, like not explicitly stating that parentId refers to an area widget, but overall this is highly complete for a creation tool.

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 0% (widgets is just an array of objects with additionalProperties: true), so the description must compensate. It does so thoroughly by enumerating every widget property (x, y, shape, text, htmlText, width, height, style, parentId) and listing all valid shape values, significantly exceeding minimal schema info.

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 one or more shape widgets on a mural', which is a specific verb+resource combination. It clearly distinguishes this from sibling tools like create_sticky_notes or create_textboxes by focusing on shape widgets, and the shape list reinforces the specific scope.

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 description implies when to use the tool (when you need shape widgets) but provides no explicit comparison or exclusions relative to sibling create tools. There is no 'use this instead of X' guidance, so it relies on the reader to infer the distinction.

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