Skip to main content
Glama

Hunter Pūteanui (hcIfU)

extract_webpage_markdown

Read-onlyIdempotent

Convert a public URL or raw HTML snippet into clean Markdown, title, and excerpt.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "extract_webpage_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOptional URL to extract into clean Markdown
formatNojson_bundle or zip_base64json_bundle
base_urlNoOptional domain to audit for MCP & x402 conformance
workloadNocoding, search, or generalcoding
tools_csvNoOptional comma-separated tool names for FastMCP scaffoldping,fetch_summary
html_inputNoOptional raw HTML to extract into clean Markdown
amount_usdcNoPay what you can afford in USDC (minimum 0.01 — e.g. 0.01, 0.10, 2.00, 100.00). Every amount receives the full package.
descriptionNoOptional custom FastMCP server descriptionCustom FastMCP Server
server_nameNoOptional custom FastMCP server name to scaffoldcustom_tools

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior, so the safety profile is covered. The description adds only that the source must be public; it says nothing about the payment requirement implied by amount_usdc or about rate limits, fetch failures, or how URL vs. html_input precedence is resolved.

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 front-loaded sentence with zero filler that names the input types and the returned fields. It is efficient, though its brevity contributes to the under-specification of a nine-parameter tool.

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 nine parameters, no required fields, no output schema, and apparent bundled capabilities (payment, scaffolding, auditing) implied by the schema, one sentence about Markdown extraction is not enough. The description leaves an agent unable to understand why most of the parameters exist or how they interact with the extraction behavior.

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 default baseline of 3 applies and the schema fully documents each parameter including format, workload, and amount_usdc. The description adds no meaning beyond what the schema states and never explains the precedence between url and html_input.

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 and resource ('Convert a public URL or raw HTML snippet into clean Markdown, title, and excerpt'), so the primary function is immediately legible. It does not differentiate from siblings such as generate_fastmcp_scaffold or audit_agent_endpoint, even though the schema (server_name, tools_csv, base_url) suggests overlapping capabilities, which leaves ambiguity about the tool's full scope.

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 when-to-use guidance, no prerequisite notes, and no named alternatives. The single word 'public' hints at an access constraint, but an agent gets no direction on choosing this over a sibling or on what to do when HTML must come from a private source.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources