Skip to main content
Glama
Sign In
Devin Search MCP

Devin Search MCP

by soulvon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

devin_web_fetch

Fetches a web page and removes navigation, ads, and scripts to return clean Markdown, plain text, or a summary.

Instructions

轻量抓取指定网页的正文内容，自动剔除导航、广告与脚本，输出整洁的 Markdown 或纯文本。

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

Input Schema

NameRequiredDescriptionDefault
urlYes目标网页完整 URL (http/https)
extract_modeNo输出格式markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / properties / extract_mode / description
      Previous value: -"正文提取格式: 'markdown' (结构化文档，默认), 'text' (纯文本), 'summary' (核心要点摘要)"New value: +"输出格式"
    • changedInput schema / properties / url / description
      Previous value: -"目标网页的完整 URL (必须以 http:// 或 https:// 开头)"New value: +"目标网页完整 URL (http/https)"
  2. First observedv1.0.6

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that navigation, ads, and scripts are stripped and that output is cleaned Markdown/text, but says nothing about JS-rendered pages, redirect/timeout/error behavior, auth-gated content, or size limits — notable gaps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, well-formed sentence that front-loads the action and scope, then the value-add (content cleaning) and output form. Nothing is padded or 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 two-parameter fetch tool with no annotations or output schema, the description covers what it does and the output flavor, but omits the third output mode ('summary'), and any failure/rendering behavior an agent would need to call it confidently.

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 schema already documents both parameters, establishing a baseline of 3. The description only loosely echoes the output-format parameter and, notably, mentions just 'Markdown 或纯文本' while the enum also includes 'summary', so it adds no meaning beyond the schema and slightly under-describes it.

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 names a specific verb (抓取/lightweight fetch) and resource (指定网页的正文内容), and adds what distinguishes the result (自动剔除导航、广告与脚本). It is clearly a fetch tool rather than a search tool, but it never explicitly names or contrasts with its sibling devin_web_search.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. The word 轻量 hints at a lightweight/limited tradeoff but never states the condition (e.g. JS-heavy pages, pages needing rendering) or points to an alternative tool such as devin_web_search. The agent must infer routing from the phrase alone.

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