Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Get a website as clean Markdown

get_website_markdown
Read-onlyIdempotent

Convert web pages into clean Markdown by crawling site links or web search results, removing navigation, ads, and footers for RAG, AI agents, documentation import, and content audits.

Instructions

Reads web pages and returns their main content as clean Markdown (navigation, ads and footers removed), with title, URL, word count and headings: start from site links and follow links on the same site, or start from web search words. Useful for RAG, AI agents, documentation import and content audits. Runs the Apify Actor tacps126/website-markdown on your Apify account (about $0.001 per page; spend per call is capped at $0.5).

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

Input Schema

NameRequiredDescriptionDefault
urlsNoStart pages, e.g. ["https://docs.apify.com/academy"].
queriesNoWeb search words; the top results are read.
max_depthNoHow many links deep to follow from a start page (0 = start pages only).
max_itemsNoMaximum results to return (default 50, max 1000). Cost scales with this.
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
max_pages_per_siteNoPages to read per site.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.19.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations (readOnly/openWorld/idempotent/non-destructive) by disclosing the underlying Apify Actor, per-page cost (~$0.001), and a hard per-call spend cap of $0.5 — details an agent needs before launching a crawl. It also describes the output shape and the content-cleaning behavior, which the annotations do not cover.

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?

Front-loaded with the core verb and return shape, then modes, then use cases, then cost. Three dense sentences with little waste, though the 'Useful for RAG, AI agents, documentation import and content audits' list is closer to discovery padding than operational guidance.

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

Completeness5/5

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

An output schema exists and annotations cover the safety profile, so the remaining burden is cost, origin, and crawl semantics — all supplied. Nothing an agent needs to invoke this correctly (inputs, cost ceiling, what gets returned) is missing.

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 all six parameters are already documented in the schema, setting the baseline at 3. The description adds only indirect parameter meaning — the $0.5 spend cap, which informs how aggressively max_items and max_depth should be set — but does not explain any parameter directly.

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?

States a specific verb and resource ('Reads web pages and returns their main content as clean Markdown') plus exactly what is stripped (navigation, ads, footers) and what is returned (title, URL, word count, headings). Combined with the title and the crawl-mode sentence, an agent can tell this apart from the sibling scrapers/aggregators without opening the schema.

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?

Clearly frames the two entry modes ('start from site links and follow links on the same site, or start from web search words') and lists concrete use cases (RAG, AI agents, documentation import, content audits). It never names a sibling tool or states when not to use it, so there is context but no explicit exclusions or alternatives.

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