Skip to main content
Glama

clear_preview

Stops the CSS preview on a shared browser tab, restoring the page to its original styles. Use the tab handle from list_tabs, or omit it when only one tab is shared.

Instructions

Remove the CSS preview from a tab.

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": "clear_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations are empty, so the description carries the full burden and mostly doesn't. It doesn't say whether the removal is reversible, whether it targets only the last preview or all previews on the tab, what happens if no preview exists, or whether a page reload is needed.

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?

One short, front-loaded sentence with no filler. It is efficient, though its brevity is part of the under-specification problem rather than a virtue.

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

Completeness2/5

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

Even for a single-parameter mutation tool, the definition is thin: no annotations, no output schema, and no statement of effect or failure modes. An agent knows roughly what it does but not enough to invoke it confidently against delete_style.

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% and the single 'tab' parameter already documents its format and the 'optional when only one tab is shared' fallback. The description adds only the phrase 'from a tab', which mildly reinforces the target but adds no meaning beyond the schema.

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?

States a specific verb and resource: 'Remove the CSS preview from a tab.' An agent can tell this undoes a preview, but the description never distinguishes it from delete_style or apply_css, which sit in the sibling list and could plausibly do overlapping things.

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

Usage Guidelines2/5

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

No when-to-use guidance at all. It doesn't say whether this is for undoing an apply_css preview versus permanently deleting an injected style (delete_style), nor does it state prerequisites such as an active preview existing.

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