Skip to main content
Glama
Sign In
agent-browser-mcp

agent-browser-mcp

by zy2755
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_type

Types text into input, textarea, or contenteditable fields, clearing existing content first and optionally pressing Enter to submit.

Instructions

向输入框输入文本(先清空再输入)。submit:true 时回车提交。适用于 input/textarea/contenteditable。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "browser_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNo
textYes要输入的文本
clearNo是否先清空(默认 true;false 则追加)
submitNo输入后按 Enter(默认 false)
selectorNo
timeoutMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose two meaningful behaviors: the field is cleared before typing (with the schema noting clear=false appends) and submit=true fires Enter. It says nothing about how the target is resolved, what happens on timeout, or whether the action fails silently, which are the risky behaviors for an unannotated mutation tool.

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?

Three short sentences, front-loaded with the core action and the clearing behavior, followed by the submit side effect and applicability scope. Nothing is redundant.

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?

For a 6-parameter, unannotated, no-output-schema tool the description covers the core action and side effects, but leaves the ref-vs-selector targeting question and timeout semantics entirely unaddressed. Adequate to invoke in the simple case, incomplete for the ambiguous ones.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: text, clear, and submit are documented in the schema, and the description only restates clear/submit behavior. The two targeting parameters (ref and selector) and timeoutMs are undocumented in both places, so an agent gets no guidance on which targeting mechanism to supply or how they interact.

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?

The description states a specific verb and resource ('向输入框输入文本') and scopes the applicable element types (input/textarea/contenteditable), which separates it from siblings like browser_press_key or browser_select_option. It stops short of naming an alternative explicitly, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

Applicability is implied by the element-type list and the submit flag describes one usage mode, but there is no explicit when-to-use/when-not-to-use guidance and no pointer to siblings for key presses, selection, or reading values. Usage must be inferred from the target-element constraint.

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