Skip to main content
Glama

webmd__extract

Convert any public web page to clean Markdown, extract HTML tables to JSON, pull JSON-LD, or crawl a whole site's sitemap and get Markdown for up to 25 pages in one call. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/webmd/extract

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

Input Schema

NameRequiredDescriptionDefault
maxNoFor /sitemap: max pages, default 10, cap 25
urlYesPublic page URL
modeNoExtraction mode

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / max
      Added value: +{
      +  "description": "For /sitemap: max pages, default 10, cap 25",
      +  "type": "integer"
      +}
    • addedInput schema / properties / mode
      Added value: +{
      +  "description": "Extraction mode",
      +  "enum": [
      +    "text",
      +    "article",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / url / description
      Added value: +"Public page URL"
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / required
      Added value: +[
      +  "url"
      +]
  2. Changed3 schema fields changed
    • removedInput schema / properties / chars
      Removed value: -{
      -  "description": "Max characters of markdown to return (default 4000)",
      -  "maximum": 50000,
      -  "minimum": 200,
      -  "type": "integer"
      -}
    • removedInput schema / properties / url / description
      Removed value: -"Public http(s) page URL to extract"
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  3. Changed3 schema fields changed
    • addedInput schema / properties / chars
      Added value: +{
      +  "description": "Max characters of markdown to return (default 4000)",
      +  "maximum": 50000,
      +  "minimum": 200,
      +  "type": "integer"
      +}
    • addedInput schema / properties / url / description
      Added value: +"Public http(s) page URL to extract"
    • addedInput schema / required
      Added value: +[
      +  "url"
      +]
  4. Changed3 schema fields changed
    • removedInput schema / properties / chars
      Removed value: -{
      -  "description": "Max markdown characters to return.",
      -  "type": "number"
      -}
    • removedInput schema / properties / url / description
      Removed value: -"Public http(s) page to convert."
    • removedInput schema / required
      Removed value: -[
      -  "url"
      -]
  5. Changed5 schema fields changed
    • addedInput schema / properties / chars
      Added value: +{
      +  "description": "Max markdown characters to return.",
      +  "type": "number"
      +}
    • removedInput schema / properties / links_max
      Removed value: -{
      -  "description": "Max links to list (0-1000, default 200)",
      -  "type": "integer"
      -}
    • changedInput schema / properties / url / description
      Previous value: -"Absolute public http(s) URL to extract"New value: +"Public http(s) page to convert."
    • removedInput schema / properties / urls
      Removed value: -{
      -  "description": "Batch (POST only): array of up to 10 URLs to extract in one call",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • addedInput schema / required
      Added value: +[
      +  "url"
      +]
  6. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the critical traits: a per-call charge of $0.01 in USDC on Base (eip155:8453), the x402 payment location in params._meta, and the HTTP method and endpoint. It lacks detail on failure behavior, rate limits, or what happens when payment is missing, so it stops short of a 5.

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?

It leads with the capabilities, then pricing, then transport, so the most decision-relevant content comes first. The single long sentence is dense but every clause carries information; only the overlapping capability list feels somewhat redundant with sibling tools.

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?

Payment mechanics, endpoint and scope are covered, which is what an agent most needs to invoke it. The gaps are the undefined extraction modes and the unresolved relationship to sibling tools that appear to do the same jobs, leaving the caller to guess which call to make.

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 reinforces the 25-page cap implied by 'max' but adds nothing about the meaning or effect of the mode values text/article/full, which remain undefined in both schema and description.

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 concrete verbs and outputs (convert to Markdown, extract tables to JSON, pull JSON-LD, crawl a sitemap) against a generic name like 'extract', so an agent can tell what it produces. It does not, however, distinguish itself from the sibling tools webmd__tables, webmd__jsonld and webmd__sitemap, which appear to perform the same individual capabilities.

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 or when-not-to-use guidance. The description never says why an agent would choose this four-in-one call over webmd__tables, webmd__jsonld, webmd__sitemap or web_extract__extract, which is exactly the ambiguity an agent needs resolved.

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