Skip to main content
Glama
Sign In
brightdata

Bright Data MCP

Official
by brightdata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

scrape_as_markdown

Read-only

Fetches a web page and returns its content as Markdown by default, with options for plain text, raw HTML, or schema.org JSON data.

Instructions

Fetch one web page. Returns JSON: url, title, format, content. content is the page in one format, markdown by default. Pick another with the format param:

  • text: plain text, no links or headings

  • html: raw HTML, for CSS selectors or data hidden in the markup

  • ld_json: schema.org data (price, rating, author...) If the page has no data in that format, markdown is returned instead, with a note. No JavaScript rendering. Pages that take longer than 45 s time out.

Input Schema

NameRequiredDescriptionDefault
urlYes
formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.2.0
    • addedInput schema / properties / format
      Added value: +{
+  "default": "markdown",
+  "enum": [
+    "markdown",
+    "text",
+    "html",
+    "ld_json"
+  ],
+  "type": "string"
+}
  2. Addedv2.9.3

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, openWorld, non-destructive), and the description adds materially beyond them: no JavaScript rendering, a 45 s timeout, the silent fallback to markdown with a note, and the exact JSON response shape. These are exactly the failure modes an agent needs to anticipate before calling.

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?

Purpose and return shape are front-loaded, the format options are a tight scannable list, and the limitations close it out. No sentence is redundant and the ordering matches the agent's decision sequence.

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 two-parameter fetch tool with no output schema, the description supplies the return fields, the format contract, the fallback behaviour, and the two operational limits (no JS, 45 s timeout). Nothing an agent needs to invoke it correctly or interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description has to carry parameter meaning — and it does, defining all four format enum values with concrete use cases and the default/fallback rule. The url parameter gets only "one web page", with no note on redirects or URL constraints, so it isn't fully compensated.

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 ("Fetch one web page") and immediately enumerates the return fields, so the agent knows exactly what the tool produces. It implicitly distinguishes itself from scrape_batch via "one web page" but never names the sibling that shares its territory (scrape_as_html), so differentiation is inferred rather than stated.

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?

Gives clear selection guidance for the format parameter (when to pick text, html, or ld_json) and the default behaviour when a format is unavailable. It lacks explicit when-not-to-use routing — nothing says to use scrape_batch for multiple URLs or scrape_as_html rather than format=html — which keeps it below a 5.

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