Skip to main content
Glama
mcp-toolkit

mcp-toolkit

by Dongnb66

webpage_extract

Fetch a webpage and extract its title, section headings, link list, and plain body text as structured content for analysis or indexing.

Instructions

抓取网页并抽取纯文本:返回标题、各级标题、链接列表与去标签正文,适合做网页内容的结构化提取。

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": {
      "url": "<url>"
    },
    "name": "webpage_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes目标网页 URL
timeoutMsNo请求超时毫秒,默认 10000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does well on output shape — naming title, heading levels, links, and cleaned body text — which matters because there is no output schema. However, for a network-facing tool it says nothing about failure modes, redirect/robots/auth behavior, JavaScript-rendered pages, or what happens on timeout (the only tunable it exposes besides the URL). That is a meaningful disclosure gap for a fetch tool.

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?

A single sentence with the verb-resource pairing front-loaded and the return payload enumerated after the colon; nothing is redundant or padded. A 5 would require the usage caveat to be integrated as tightly as the output list, rather than tacked on as a vague trailing clause.

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 two-parameter tool with no output schema, the description compensates well by enumerating the returned fields, so an agent knows it gets structured text rather than raw HTML. It is only slightly incomplete: no statement about error behavior or about whether dynamic/rendered content is captured.

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 both parameters (url, timeoutMs with its 10000ms default) are already documented inline, so the baseline of 3 applies. The description adds no extra meaning such as accepted URL schemes or what a shorter timeout implies for large pages.

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?

"抓取网页并抽取纯文本" names a specific verb pair (fetch + extract) and a specific resource (webpage), and the colon-list enumerates exactly what comes back (title, headings, links, tag-stripped body). The purpose is unambiguous even without opening the schema. It does not explicitly differentiate itself from any sibling (e.g. text_chunk, which may consume the output), so it stops short of 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?

"适合做网页内容的结构化提取" implies the intended context but gives no when-not conditions, no prerequisites, and no named alternative for cases like raw HTML retrieval or chunking. Usage is inferable rather than stated, which is the definition of implied guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.