Skip to main content
Glama

automate_website

Run browser actions on the active webpage through the local Chrome extension bridge: take screenshots, scrape text, click, fill forms, scroll, navigate, or extract HTML.

Instructions

Executes custom browser actions on the currently active webpage via the local Chrome extension bridge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe targeted script action. Supported actions: 'take_screenshot' (capture visual PNG screenshot of the tab for multimodal vision), 'scrape_data' (get text content), 'click_button' (click element by selector), 'fill_form' (type into input/textarea), 'get_elements' (query elements), 'scroll' (scroll down/up), 'navigate' (open URL), 'get_html' (extract HTML).
payloadNoKey-value parameters needed for the action (e.g. { selector: 'button.submit' }, { selector: 'input[name=q]', value: 'search text' }, { direction: 'down', amount: 500 }, { url: 'https://example.com' })

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only discloses the transport (local Chrome extension bridge), omitting that several actions are mutating (click_button, fill_form, navigate), whether they require user-visible permission, what happens on failure, or what the result looks like. For a tool that can drive page state, that is a significant omission.

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?

A single front-loaded sentence with no filler. It conveys verb, resource, and mechanism without redundancy, which is exactly the right size for this tool.

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

Completeness3/5

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

The parameters are fully documented via schema, but with no annotations and no output schema the description should still flag operational requirements (extension installed, tab focused) and the mutating nature of several actions. It leaves an agent to infer those, so it is minimally adequate rather than complete.

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 description coverage is 100% and the action enum-like list plus payload examples are fully documented in the schema, so the baseline of 3 applies. The description adds no syntax, format, or default information beyond what the schema already conveys.

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: executes browser actions on the currently active webpage. It also names the execution channel (local Chrome extension bridge), which tells an agent what this tool is. It does not enumerate the action types, but the schema covers that, so the gap is minor and there are no siblings to differentiate from.

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?

There is no when-to-use or when-not-to-use guidance, no alternatives, and no stated prerequisite such as an active tab or an installed extension. The phrase 'currently active webpage' gestures at context but does not say when an agent should reach for this tool.

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