Skip to main content
Glama
aashuchahal4-crypto

creatoros-mcp

by aashuchahal4-crypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

creatoros_extract

Extracts readable main content from any public web page URL, strips ads and navigation, and converts it into clean Markdown for LLM summarization and RAG pipelines.

Instructions

Extracts readable main content from any public web page URL and converts it into clean, noise-free Markdown optimized for LLM context, summarization, and RAG pipelines. Strips advertisements, navigation headers, cookie banners, and scripts while preserving headings, lists, tables, and code blocks.

When to use:

  • Call this tool when the user provides a specific URL or asks to read, scrape, summarize, or analyze documentation, blog posts, news articles, or API references from the web.

When NOT to use:

  • Do not use for keyword searches without a known URL (use creatoros_search instead).

  • Do not use for private intranet pages or sites behind interactive authentication/login walls.

Behavior:

  • Idempotent and read-only. Does not mutate server state.

  • Returns extracted Markdown as plain text.

Input Schema

NameRequiredDescriptionDefault
urlYesThe fully-qualified HTTP or HTTPS URL of the public web page to fetch and convert (e.g. "https://docs.python.org/3/tutorial/").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.1
    • changedInput schema / properties / url / description
      Previous value: -"The public web page URL to fetch and convert into Markdown (e.g. https://example.com/blog)."New value: +"The fully-qualified HTTP or HTTPS URL of the public web page to fetch and convert (e.g. \"https://docs.python.org/3/tutorial/\")."
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / properties / url / pattern
      Added value: +"^https?:\\/\\/.+"
  2. First observedv0.1.0

TDQS

A4.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 well: it declares read-only/idempotent behavior, states no server state is mutated, describes what content is stripped (ads, nav, cookie banners, scripts) and what is preserved, and specifies the return format as plain-text Markdown. It stops short of covering failure modes or rate limiting, so it is strong but not exhaustive.

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 summary followed by clearly labeled use/avoid/behavior sections, which makes scanning easy. Slightly padded by the marketing-tinged 'optimized for LLM context, summarization, and RAG pipelines' clause that doesn't change agent behavior.

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?

For a one-parameter read tool with no output schema and no annotations, the description covers purpose, exclusions, safety profile, transformation behavior, and return type. An agent has everything needed to call it correctly and interpret the response.

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% with a single required 'url' parameter already documented with format, pattern, and an example. The description reinforces the 'public web page' constraint but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 ('extracts readable main content from any public web page URL' and 'converts it into clean Markdown'), and explicitly distinguishes itself from the sibling creatoros_search by scope (known URL vs. keyword search). An agent can pick between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Has explicit 'When to use' and 'When NOT to use' sections, naming the alternative tool (creatoros_search) for the no-URL case and excluding auth-walled/intranet pages. Nothing is left to inference.

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