Skip to main content
Glama

Create an OBS overlay widget

create_obs_widget
Read-onlyIdempotent

Build a ready-to-paste Browser source URL for OBS, Streamlabs, Meld or TikTok LIVE Studio: a countdown (fixed length or until a date), a stream uptime timer, a clock in any time zone, or a goal progress bar (manual value or live TikTok follower count). Widgets are transparent, free and keep all settings in the URL, so nothing is stored. Returns the URL, the source width and height, setup steps and a link to fine-tune it visually.

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": {
      "widget": "<widget>"
    },
    "name": "create_obs_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontNoGoogle Font for the text (default Inter).
goalNogoal_bar: target number (default 100).
sizeNoText size in px.
colorNoText colour, hex like #ffffff.
labelNocountdown / stream_timer: text above the time, e.g. "Starting soon" or "Live for".
titleNogoal_bar: title, default "Follower goal".
untilNocountdown: count down to this ISO 8601 date-time with UTC offset, e.g. 2026-12-31T20:00:00-05:00.
hour12Noclock: 12-hour clock with AM/PM.
widgetYes
currentNogoal_bar: current number for a manual bar.
minutesNocountdown: length in minutes (default 5). Ignored when "until" is set.
secondsNoclock: show seconds.
end_textNocountdown: text shown when it reaches zero (default "We're live!").
timezoneNoclock: IANA time zone such as "Europe/Warsaw". Defaults to the computer running OBS.
show_dateNoclock: show the date.
show_daysNocountdown / stream_timer: show days for long durations.
hide_at_endNocountdown: hide the widget when it ends.
accent_colorNocountdown: progress bar colour; goal_bar: bar start colour.
progress_barNocountdown: show a progress bar.
show_timezoneNoclock: show the time zone name.
accent_color_2Nogoal_bar: bar end colour (gradient).
tiktok_usernameNogoal_bar: follow a TikTok account's live follower count instead of a manual number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds genuinely new behavior: nothing is stored because all settings live in the URL, and the return payload includes the URL, width/height, setup steps and a tuning link. That statelessness detail is the kind of context annotations cannot convey.

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?

Front-loaded with the action and target platforms, then widget variants, then return contents — a sensible order with no filler. It is dense but each clause carries information; the only mild weakness is that the widget list and return list are packed into two long sentences.

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?

For a 22-parameter generator with no output schema, the description compensates by spelling out what comes back (URL, width, height, setup steps, tuning link) and that no state is persisted. Remaining gaps, such as whether the returned URL is long-lived or how defaults are applied, are minor.

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 95%, so the schema already documents all 22 parameters including the minutes-vs-until interaction. The description adds only light mapping, noting countdown can be 'fixed length or until a date' and goal_bar can be 'manual value or live TikTok follower count', which largely restates what the schema says. Baseline 3 is appropriate.

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?

Opens with a specific verb and artifact ('Build a ready-to-paste Browser source URL for OBS, Streamlabs, Meld or TikTok LIVE Studio') and then enumerates the four widget kinds it produces. An agent can immediately tell this generates overlay URLs rather than stream settings or text styling, distinguishing it from every listed sibling.

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 makes the use context clear (OBS/Streamlabs overlay sources) and hints at a follow-up ('a link to fine-tune it visually'), but never states when to prefer it over alternatives or any preconditions/exclusions. Guidance is implied by the widget enumeration rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources