Skip to main content
Glama

create_sticky_notes

Create one or more sticky notes on a Mural, customizing each note's text, style, and position coordinates.

Instructions

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

Each widget object supports:
  - x, y (required): Position in px.
  - shape (required): "circle" or "rectangle".
  - text: Plain text content.
  - htmlText: HTML-formatted text (overrides text).
  - width, height: Size in px (default 138).
  - style: { backgroundColor, bold, italic, underline, strike, font, fontSize, textAlign, border }.
  - parentId: ID of parent area widget.
  - tags: Array of tag IDs.

Args:
    mural_id: The mural ID.
    widgets: Array of sticky note 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?

No annotations provided, so description must carry behavioral burden. It discloses a 1000-widget limit, required fields (x, y, shape), htmlText overriding text, and default size. But it does not mention response format, error conditions, rate limits, or authentication requirements.

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?

Structured with a clear opening sentence, bullet list for widget properties, and args section. Slightly lengthy but every detail serves a purpose; no redundancy.

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?

With an output schema present, description need not explain return values. It covers core behavior, parameters, and key constraints. Missing details like error handling or edge cases, but adequate for a creation tool given schema enrichment.

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 has 0% description coverage for parameters. The description thoroughly documents both top-level args (mural_id, widgets) and all nested widget properties (x, y, shape, text, htmlText, width, height, style, parentId, tags), adding meaning far beyond the raw 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?

Description states 'Create one or more sticky note widgets on a mural (limit 1000)' with a specific verb and resource. It clearly differentiates from sibling tools like create_shapes or create_textboxes by focusing on sticky note widgets.

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?

No explicit when-to-use vs alternatives or exclusions. However, the name and description imply use for sticky notes, and sibling context makes the distinction clear. Lacks direct guidance on choosing this tool over create_textboxes or create_shapes.

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