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

mcp-browser-search

by HeiBai-king
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

web_read

Extracts the text content of the current browser tab without navigating, so you can read page content after clicking links or paginating.

Instructions

读取当前浏览器标签页的正文（不导航）。适合点完链接或翻页之后取内容。

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

Input Schema

NameRequiredDescriptionDefault
maxCharsNo正文最大字符数，默认 200000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description must disclose the full behavioral profile. It usefully states that no navigation occurs and that only the current tab's main text is read, but it says nothing about waiting for page load, handling of blank or loading tabs, or extraction format.

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?

Two short sentences with zero waste; the scope constraint (no navigation) and the usage cue each earn their place and are 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 simple no-annotation, no-output-schema read tool with one optional parameter, the description covers the essential task and its non-navigating constraint. Edge cases such as a blank tab or a page still loading remain unaddressed, which is a minor gap.

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?

There is one parameter, maxChars, and schema description coverage is 100%, so the schema already documents its meaning and default (200000). The description adds nothing about truncation behavior or how the limit interacts with the returned text, so baseline 3 applies.

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: reads ('读取') the main body text ('正文') of the current browser tab. The parenthetical '不导航' implicitly distinguishes it from web_open, but no sibling is named explicitly, so it falls short of the clearest possible differentiation.

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 gives clear usage context: use it after clicking a link or paginating to get content ('适合点完链接或翻页之后取内容'). It does not explicitly name web_open as the alternative for navigation, though '不导航' hints at that exclusion.

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