Skip to main content
Glama

studio_goto

Navigate to a URL with a branded transition card that hides loading flashes and displays chapter titles. Waits for real content to appear before lifting the card.

Instructions

Navigate to a URL behind a designed transition card (eyebrow + big title on the theme background) — the viewer never sees a loading flash or half-hydrated page. Use for the opening shot AND every surface change; give each a short title so the cut reads as a chapter. Waits for real content (network settle + optional wait_for selector + skeleton loaders cleared) before lifting the card.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute URL to navigate to, including scheme. Example: 'https://app.example.com/dashboard'.
titleNoBig title on the transition card — usually the surface name. Optional but recommended so each cut reads as a chapter.
eyebrowNoSmall uppercase kicker on the transition card, e.g. 'DASHBOARD'. Optional.
dwell_msNoMinimum time the card stays up so the title reads, in milliseconds. Optional; default 1200.
wait_forNoCSS selector that must be visible before the card lifts (on top of network-settle + skeleton clearing). Optional; use it when the real content is gated behind a spinner. Example: '[data-loaded=true]'.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It details that the tool waits for network settle, optional wait_for selector, and skeleton loaders before lifting the card, which is good behavioral transparency. It does not mention auth or rate limits, but these are less critical for a navigation tool.

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 description is a single paragraph but well-structured, front-loading the purpose, then usage, then behavior. It is concise yet informative, though could be slightly tighter.

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 5 parameters, one required, and no output schema, the description covers the tool's behavior (transition card, waiting conditions) well. It omits return values but that's acceptable without an output schema. The context is sufficient for an agent to use the tool 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 coverage is 100%, so the description adds minimal value beyond the schema. For example, it adds 'usually the surface name' for title and example 'DASHBOARD' for eyebrow, but these are marginal. Baseline 3 is appropriate given high schema coverage.

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 navigates to a URL with a transition card to avoid loading flash. It distinguishes from sibling tools like studio_click (click action) and studio_narrate, etc., making the purpose specific and unambiguous.

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 advises using this for 'the opening shot AND every surface change', giving clear context for when to invoke it. However, it does not explicitly state when not to use it or compare with alternatives like studio_click for navigation, slightly limiting the guidance.

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/AIOProductOS/studio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server