Skip to main content
Glama
Sign In
AIOProductOS Studio

AIOProductOS Studio

Official
by AIOProductOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

studio_end_card

Display a closing card with product title, subtitle, and call-to-action URL to summarize the video and guide viewers to the next step.

Instructions

Show the closing card — a centred glass card over the (still visible) product: title, optional subtitle and URL. The classic outro: what they saw + where to get it. Hold ~2.5s after this, then studio_finish.

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": {
      "title": "<title>"
    },
    "name": "studio_end_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoCall-to-action URL shown beneath the title, e.g. 'aioproductos.com'. Optional; shown as text, not a live link.
titleYesBig closing line — the product name or the one-line takeaway. Required. Example: 'AIOProductOS'.
subtitleNoOne supporting line under the title, e.g. a tagline. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.3
    • changedInput schema / properties / subtitle / description
      Previous value: -"One supporting line (optional)."New value: +"One supporting line under the title, e.g. a tagline. Optional."
    • changedInput schema / properties / title / description
      Previous value: -"Big closing line, e.g. the product name or the takeaway."New value: +"Big closing line — the product name or the one-line takeaway. Required. Example: 'AIOProductOS'."
    • changedInput schema / properties / url / description
      Previous value: -"Call-to-action URL shown under the title (optional)."New value: +"Call-to-action URL shown beneath the title, e.g. 'aioproductos.com'. Optional; shown as text, not a live link."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are provided, so the description fully carries the burden. It details visual behavior (centred glass card over still visible product), timing (~2.5s hold), and clarifies that the URL is shown as text, not a live link. This provides adequate transparency for the agent to understand the effect.

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 two sentences long with no wasted words. It front-loads the purpose ('Show the closing card') and immediately follows with visual and functional details. Every sentence earns its place.

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 simple UI tool with 3 parameters and no output schema, the description covers the visual output, behavior, and integration with studio_finish. It does not mention error scenarios or edge cases, but for typical use, it is sufficiently complete.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds value beyond the schema: it clarifies that the subtitle is 'one supporting line under the title', the title is 'the big closing line', and the URL is displayed as text, not a link. These details enrich the schema descriptions.

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 clearly states the tool shows a closing card with a title, optional subtitle, and URL, placed as a centred glass card over the visible product. It distinguishes itself by specifying it is 'the classic outro' and explicitly mentions the subsequent step (studio_finish), differentiating it from siblings like studio_caption or studio_highlight.

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

Usage Guidelines4/5

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

The description provides a clear usage hint: 'Hold ~2.5s after this, then studio_finish', indicating this tool should be used before studio_finish as the closing step. It does not explicitly state when not to use or mention alternatives, but the context of a sequence makes the guidance sufficient.

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

Deploy Server

Other Tools