Simpler.Asia

studio.add_sticker

Add a sticker/element overlay (creator CTAs, emojis, shapes) at a normalized position with its own time range and animation.

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": {
      "project_id": "<project_id>",
      "sticker": "<sticker>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "studio.add_sticker"
  }
}

Input Schema

Name	Required	Description	Default
`x`	Yes	0-1
`y`	Yes	0-1
`emoji`	No	Emoji glyph when the sticker is an emoji.
`sticker`	Yes	Catalog key (e.g. subscribe, sale, live) or emoji name.
`animation`	No		none
`project_id`	Yes	The studio project (vp_…) this tool acts on.
`duration_ms`	No
`start_time_ms`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The readOnlyHint=false annotation already establishes that this is a mutation. The description adds useful behavioral context that the overlay has its own time range and animation, but it does not cover catalog lookup behavior, permissions, or what is returned after creation.

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?

The definition is a single front-loaded sentence with parenthetical examples and no wasted text. It is dense but appropriately sized for the tool's scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The core purpose and timing/position behavior are covered, and the schema supplies required fields and enums. But with 8 parameters, no output schema, and ambiguous sticker/emoji semantics, the description leaves meaningful gaps about correct invocation and the result of adding a sticker.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 63%, and the description adds some meaning by clarifying that x/y are normalized and that the overlay has its own time range, which implicitly covers start_time_ms and duration_ms that lack schema descriptions. However, it does not resolve how the sticker and emoji parameters interact (catalog key versus emoji name/glyph).

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 states a specific verb and resource: add a sticker/element overlay, with examples like creator CTAs, emojis, and shapes. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as studio.add_text_overlay or studio.update_sticker.

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?

Usage is implied by the examples and the overlay/position/time-range framing, but there is no explicit guidance on when to use this versus studio.update_sticker, studio.add_text_overlay, or other overlay insertion tools. No exclusions or alternatives are named.

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

All Simpler.Asia 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?