抓取一个公开网页，返回干净的 Markdown（供 AI 阅读/总结/提取）。
只抓公开网页，禁止内网/保留地址；不生成任何内容，只做抓取与格式转换。 静态抓取拿不到内容的 JS 动态页可加 render=true 走真浏览器渲染。
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | 要抓取的网页 URL（http/https，仅限公开网页） | |
| render | No | 经境内托管浏览器真渲染 JS 后再抽取（适合动态页），默认关闭 | |
| formats | No | 输出格式子集：markdown / html / text，默认 markdown | |
| only_main_content | No | 只提取正文主体，去掉导航/广告/页脚 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden and discloses key behaviors: it only fetches and converts, does not generate content, and uses real browser rendering when render=true. It stops short of describing error handling or details for all parameters, but the essential traits are covered.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is only two sentences, front-loaded with the core purpose, and includes a practical usage tip without any redundant or filler wording. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 4 parameters and no output schema, the description covers the primary use case, constraints, and advanced rendering option. It does not mention the formats or only_main_content parameters, but the schema fills those gaps. A brief pointer to sibling tools would improve completeness, but it is already sufficiently informative.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema fully documents each parameter. The description adds minimal extra semantics beyond repeating the render=true suggestion already present in the schema. It meets the baseline for well-documented schemas but does not go further.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: '抓取一个公开网页，返回干净的 Markdown' (fetch a public webpage, return clean Markdown). It also clarifies the tool only fetches and converts, not generates, which differentiates it from siblings like 'extract' or 'crawl'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides clear context: only public webpages, prohibited intranet/reserved addresses, and advises using render=true for JS-heavy dynamic pages. However, it does not explicitly compare with sibling tools or state when not to use this tool in favor of alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct role: site_map discovers URLs, scrape_url fetches a single page, crawl fetches multiple pages, and extract returns structured JSON. The overlap between scrape_url and crawl is clearly addressed in descriptions by single vs multi-page, so an agent can easily select the right tool.
The names are mostly intuitive, with two verbs (crawl, extract) and two noun phrases (scrape_url, site_map). The mix of verb and noun forms is a slight inconsistency, but all names are lowercase with underscores, so the pattern is still predictable.
With only 4 tools, each serves a distinct step in the web data workflow: discovery, single-page fetch, multi-page crawl, and structured extraction. This is an appropriate scope for the server's purpose, neither too sparse nor overwhelming.
The tool set covers the full pipeline from discovering URLs (site_map) to fetching content (scrape_url, crawl) to extracting structured data (extract). There are no obvious gaps for the server's stated purpose of web data collection and transformation.