Skip to main content
Glama
Silbercue

Public Browser

by Silbercue
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

run_plan

Batch browser actions into a single server-side plan to reduce round trips. Supports variables, conditions, parallel tabs, and error handling.

Instructions

Batch the next 2+ known actions (click, type, scroll, view_page chains) here instead of N separate calls: a sequence of tool steps, executed server-side in one call. Variables via vars and saveAs ($name), conditions (if), suspend/resume to ask the agent mid-plan, errorStrategy abort | continue | capture_image, and parallel groups per tab: parallel: [{ tab, steps }].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
varsNoInitial variables, available as $name
stepsNoTool steps to run in order
resumeNoResume a suspended plan
parallelNoTab groups to run in parallel
use_operatorNoOperator mode (rule engine + micro-LLM); needs the executeOperator hook
errorStrategyNoabort stops at the first error; continue runs all steps; capture_image screenshots, then abortsabort

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed24 schema fields changedv2.10.5
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / errorStrategy
      Added value: +{
+  "default": "abort",
+  "description": "abort stops at the first error; continue runs all steps; capture_image screenshots, then aborts",
+  "enum": [
+    "abort",
+    "continue",
+    "capture_image"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / parallel / description
      Previous value: -"Array of tab groups to execute in parallel across tabs."New value: +"Tab groups to run in parallel"
    • removedInput schema / properties / parallel / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / parallel / items / properties / steps / description
      Previous value: -"Steps to execute on this tab"New value: +"Steps for this tab"
    • changedInput schema / properties / parallel / items / properties / tab / description
      Previous value: -"Tab ID (targetId) to execute steps on"New value: +"Tab ID (targetId)"
    • removedInput schema / properties / resume / additionalProperties
      Removed value: -false
    • changedInput schema / properties / resume / description
      Previous value: -"Resume a previously suspended plan."New value: +"Resume a suspended plan"
    • changedInput schema / properties / resume / properties / answer / description
      Previous value: -"Agent's answer to the suspend question"New value: +"Answer to the suspend question"
    • changedInput schema / properties / resume / properties / planId / description
      Previous value: -"ID of the suspended plan to resume"New value: +"ID of the suspended plan"
    • changedInput schema / properties / steps / description
      Previous value: -"Array of tool steps to execute sequentially."New value: +"Tool steps to run in order"
    • removedInput schema / properties / steps / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / steps / items / properties / if / description
      Previous value: -"Condition expression — step runs only if true. Use $varName for variables. Example: \"$pageTitle === 'Login'\""New value: +"Run the step only if this expression is true, e.g. \"$pageTitle === 'Login'\""
    • changedInput schema / properties / steps / items / properties / params / description
      Previous value: -"Parameters for the tool. Use $varName for variable substitution."New value: +"Tool parameters; $name substitutes a variable"
    • changedInput schema / properties / steps / items / properties / saveAs / description
      Previous value: -"Save step result as variable (accessible via $name in later steps)"New value: +"Save the result as $name for later steps"
    • removedInput schema / properties / steps / items / properties / suspend / additionalProperties
      Removed value: -false
    • changedInput schema / properties / steps / items / properties / suspend / description
      Previous value: -"Suspend plan at this step to ask the agent a question"New value: +"Pause here to ask the agent a question"
    • changedInput schema / properties / steps / items / properties / suspend / properties / condition / description
      Previous value: -"Condition expression — suspend AFTER step if true. Uses $varName syntax."New value: +"Suspend after the step if this $-expression is true"
    • changedInput schema / properties / steps / items / properties / suspend / properties / context / description
      Previous value: -"Context to include: 'capture_image' captures the page"New value: +"capture_image: attach a screenshot"
    • changedInput schema / properties / steps / items / properties / suspend / properties / question / description
      Previous value: -"Question to ask the agent when suspending"New value: +"Question for the agent"
    • changedInput schema / properties / steps / items / properties / tool / description
      Previous value: -"Tool name to execute (e.g. 'click', 'type', 'press_key', 'navigate', 'scroll')"New value: +"Tool name"
    • changedInput schema / properties / use_operator / description
      Previous value: -"Operator mode (rule engine + Micro-LLM). Requires the executeOperator hook to be registered."New value: +"Operator mode (rule engine + micro-LLM); needs the executeOperator hook"
    • addedInput schema / properties / vars
      Added value: +{
+  "additionalProperties": {},
+  "description": "Initial variables, available as $name",
+  "type": "object"
+}
  2. First observedv2.7.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses server-side execution, variable flow, conditional steps, suspend/resume behavior, error strategies, and parallel groups. It does not cover partial-failure side effects or return values, but the disclosed traits are substantial and accurate.

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 dense but efficient, conveying all major capabilities in a single compact sentence. It could benefit from a structured breakdown, but every phrase carries meaning and the core purpose is front-loaded.

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 complex tool with nested objects and no output schema, the description covers the main operational dimensions: what it batches, how variables work, control flow, suspension, error handling, and parallelism. It does not describe the plan result or how to obtain the planId after suspension, though those are partially in the schema.

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%, so the baseline is 3. The description adds a useful high-level mapping of features to concepts like $name, if, suspend/resume, errorStrategy, and parallel groups, but it does not materially deepen parameter details beyond what the schema already documents.

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 batches multiple known actions into one server-side call, explicitly naming click, type, scroll, and view_page chains. This directly distinguishes it from the individual action sibling tools and conveys its orchestration role.

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?

It says to use this 'instead of N separate calls' for '2+ known actions,' which gives a concrete condition for choosing it over individual action tools. It does not explicitly say when not to use it, but the focus on known actions implies uncertain or exploratory flows should be done step-by-step.

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/Silbercue/public-browser'

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