Skip to main content
Glama
mysleekdesigns

CrawlForge MCP Server

extract_text

Read-onlyIdempotent

Extract clean, human-readable text or markdown from any web page by removing HTML tags, scripts, and styles. Ideal for RAG workflows, keyword search, summarization, and NLP.

Instructions

Use this when you need a page's human-readable text or markdown stripped of HTML tags, scripts, and styles — e.g. for keyword search, summarization, RAG ingestion, or NLP. Use output_format:"markdown" for RAG workflows. Faster than extract_content but returns unstructured content. Example: extract_text({url: "https://example.com/article", output_format:"markdown"})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to extract text from
output_formatNoOutput format: "text" (default) or "markdown" — use markdown for RAG workflowstext
remove_stylesNoRemove style tags before extraction
remove_scriptsNoRemove script tags before extraction
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds that the tool is faster than extract_content and returns unstructured content, complementing the annotations without contradiction.

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?

The description is two concise sentences plus an example, front-loaded with purpose and use cases. No unnecessary words.

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

Completeness4/5

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

Given 4 parameters, no output schema, and the tool's simplicity, the description covers purpose, usage, and parameter hints adequately. It could mention the return format more explicitly, but 'unstructured content' suffices.

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% (all parameters described). The description adds minimal extra meaning beyond the schema, though it does provide an example and usage guidance for output_format.

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 it extracts human-readable text/markdown stripped of HTML, scripts, and styles, and distinguishes itself from the sibling tool 'extract_content' by noting it is faster but returns unstructured content.

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?

It specifies use cases (keyword search, summarization, RAG, NLP) and recommends output_format:'markdown' for RAG. It also contrasts with extract_content, though it doesn't explicitly list when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mysleekdesigns/crawlforge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server