Skip to main content
Glama
wtznicy

MyWebSearch

by wtznicy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fetchWebContent

Read-onlyIdempotent

Fetch and extract readable content from public HTTP(S) URLs, returning clean text or Markdown from web pages and Markdown files.

Instructions

Fetch content from a public HTTP(S) URL (supports Markdown files and normal web pages)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoReturn the raw response body (HTML/plain text) without extraction
urlYes
formatNoContent format: 'markdown' preserves fenced code blocks (with language) and GFM tables — better for technical docs
maxCharsNo
startIndexNoCharacter offset to start reading from (for paging through long content)
readabilityNo
includeLinksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.15
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Content format: 'markdown' preserves fenced code blocks (with language) and GFM tables — better for technical docs",
+  "enum": [
+    "text",
+    "markdown"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.11

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, open-world behavior, and the description does not contradict them. It adds only that the target should be public and that Markdown pages/pages are supported, but does not disclose extraction, paging, or failure behavior.

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?

The description is a single front-loaded sentence with no filler; it earns its place. It is concise but so minimal that it leans toward under-specification, which is penalized elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, no output schema, and specialized siblings, this one-liner leaves critical invocation details (defaults, extraction behavior, link inclusion, paging) undocumented. The agent lacks enough context to reliably call this tool correctly.

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 only 43%, and the description doesn't compensate: it never explains raw, readability, includeLinks, maxChars, or startIndex behavior. The Markdown mention is the only added parameter-related context, aligning loosely with the format enum.

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?

States a specific verb+resource ('Fetch content from a public HTTP(S) URL') and signals supported content types ('Markdown files and normal web pages'). It is clear, but it does not explicitly differentiate itself from the specialized sibling fetch tools (fetchGithubReadme, fetchCsdnArticle, fetchJuejinArticle), 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 Guidelines2/5

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

No sentence addresses when to choose this tool over siblings; the specialized fetch tools aren't mentioned, and there are no exclusions or preconditions. The only usage signal is the general 'public HTTP(S) URL' phrase, which is implicit rather than explicit guidance.

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