Skip to main content
Glama
Sign In
AIOProductOS Studio

AIOProductOS Studio

Official
by AIOProductOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

studio_zoom

Zoom the camera toward a CSS selector or visible text to highlight key content. Reset before navigating to prevent inherited zoom.

Instructions

Camera punch-in: smoothly zoom the page toward a target (CSS selector or visible text) — the money shot for a metric, button, or result. Captions stay screen-fixed; the content scales under them. ALWAYS studio_zoom with reset=true before navigating or showing the end card, or the next scene inherits the zoom.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "studio_zoom"
  }
}

Input Schema

NameRequiredDescriptionDefault
resetNotrue eases the camera back to 1:1 (call before navigating or showing the end card, or the next scene inherits the zoom). Ignores target/zoom_scale. Default false.
targetNoCSS selector or visible text to punch in on (centered). Required unless reset=true. Example: '.big-number' or 'Sign up'.
zoom_scaleNoZoom factor (>1). Optional; default 1.7. Keep ≤2.2 — beyond that the page pixelates. Ignored when reset=true.
duration_msNoZoom animation length in milliseconds. Optional; default 1100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.3
    • changedInput schema / properties / duration_ms / description
      Previous value: -"Zoom duration (optional; default 1100)."New value: +"Zoom animation length in milliseconds. Optional; default 1100."
    • addedInput schema / properties / duration_ms / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / duration_ms / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / reset / description
      Previous value: -"Ease the camera back to 1:1 instead of zooming."New value: +"true eases the camera back to 1:1 (call before navigating or showing the end card, or the next scene inherits the zoom). Ignores target/zoom_scale. Default false."
    • changedInput schema / properties / target / description
      Previous value: -"CSS selector, or visible text, to punch in on."New value: +"CSS selector or visible text to punch in on (centered). Required unless reset=true. Example: '.big-number' or 'Sign up'."
    • changedInput schema / properties / zoom_scale / description
      Previous value: -"Zoom factor (optional; default 1.7; keep ≤2.2)."New value: +"Zoom factor (>1). Optional; default 1.7. Keep ≤2.2 — beyond that the page pixelates. Ignored when reset=true."
    • addedInput schema / properties / zoom_scale / maximum
      Added value: +2.2
    • addedInput schema / properties / zoom_scale / minimum
      Added value: +1
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, but the description reveals key behaviors: captions stay screen-fixed while content scales, and failure to reset causes the zoom to persist. This adds significant context beyond the input schema.

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?

Two sentences pack the core action and the critical usage rule without superfluous words. Front-loaded with the main verb and resource.

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 zoom tool with no output schema, the description covers the action, special behavior (captions fixed), and the essential reset requirement. It is sufficiently complete for an agent to use it correctly.

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 covers all 4 parameters with descriptions. The description reinforces the importance of 'reset' and the default for 'zoom_scale', but doesn't add new meaning beyond the schema. 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?

The description clearly states the tool's purpose: 'Camera punch-in: smoothly zoom the page toward a target (CSS selector or visible text)'. It uses specific verb and resource, and the unique zooming action distinguishes it from sibling tools like studio_click 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 Guidelines5/5

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

Explicit guidelines are given: 'ALWAYS studio_zoom with reset=true before navigating or showing the end card, or the next scene inherits the zoom.' This tells when to use the tool and when not to (i.e., without reset before navigation).

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