Skip to main content
Glama
Sign In
all-agents-mcp

all-agents-mcp

by Dokkabei97
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fetch_page

Fetch web page content from any URL using Gemini's native browsing. Extract specific parts by passing an optional instruction.

Instructions

Fetch web page content via Gemini CLI. Gemini has native web browsing — use this to retrieve and extract content from URLs.

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

Input Schema

NameRequiredDescriptionDefault
urlYesTarget URL to fetch content from
modelNoGemini model to use (default: gemini-3-flash-preview)
timeoutNoTimeout in milliseconds (default: 120000)
instructionNoOptional extraction/focus instruction (e.g. 'extract only the API table')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.2

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the basic fetch action and native browsing capability, but doesn't disclose behavioral details such as rendering, output format, error handling, or potential side effects.

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 sentences, front-loaded with the core purpose. No wasted words; every sentence contributes to understanding the tool's function.

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?

The description is adequate for a simple fetch tool, but with no annotations or output schema, it could provide more context about the return format or how the instruction parameter affects extraction. The schema covers parameters well, so it is not severely incomplete.

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 coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema; it mentions 'extract content' which aligns with the instruction parameter, but doesn't elaborate on url, model, or timeout parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches web page content via Gemini CLI, with a specific verb and resource. It differentiates from sibling tools which focus on agent collaboration, code review, and testing.

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?

Provides clear context that this tool is for retrieving and extracting content from URLs, leveraging Gemini's native web browsing. It does not explicitly mention when not to use it or list alternatives, but the usage scenario is evident.

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