Skip to main content
Glama
webscraping-ai

WebScraping-AI MCP Server

Official
by webscraping-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Structured Site Data

webscraping_ai_data
Read-only

Extract structured JSON from public YouTube, TikTok, X, LinkedIn, Instagram, or Reddit URLs by auto-detecting the site and page type for parsed data.

Instructions

Get structured JSON for a public page on a supported site from its normal URL, e.g. a YouTube video, channel or playlist, a TikTok video or profile, an X post or profile, a LinkedIn company, job or profile, an Instagram post, reel or profile, or a Reddit post, subreddit or user. Returns {request_parameters: {url, provider, type}, parse_status, data}: provider (site) and type (page kind) are detected from the URL, parse_status is ok, parse_failed or not_found, and data holds snake_case fields whose shape depends on provider and type (null fields for values the page doesn't expose; data itself can be null when parsing fails). More sites are added on the server over time: an unsupported URL or page type returns a 400 error, not charged, whose message lists what is supported. For other sites, use webscraping_ai_fields. Priced per site (see https://webscraping.ai/docs#data), including parse_failed and not_found results; failed fetches are not charged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesNormal URL of a public page on a supported site, e.g. https://www.youtube.com/watch?v=dQw4w9WgXcQ. Sent as-is; the site and page type are detected from it.
paramsNoExtra site-specific query parameters sent to the API as-is, as an object of string, number or boolean values, for parameters added after this tool was released. Must not contain url, api_key or the parameters above.
countryNoTwo-letter country code of the proxy used to fetch the page, e.g. us, gb, de (us by default).
transcriptNoYouTube videos only. Also fetch the video's transcript into data.transcript (null when no matching captions are available; false by default). If the transcript fetch fails, the whole request fails with a 500 and is not charged.
transcript_languageNoYouTube videos only, with transcript: true. Caption language to pick, e.g. en, de. Without it, English is preferred, then the first available track; if the video has no captions in that language, data.transcript is null.
disable_content_sandboxingNoReturn the raw result without the external-content security boundaries that guard against prompt injection (false by default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.2

TDQS

A4.7/5.0
Behavior5/5

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

With annotations covering read-only/open-world/destructive, the description adds substantial behavioral detail: the exact return envelope, parse_status values, null-field and null-data behavior, 400 and 500 error conditions, and pricing rules including that failed fetches are not charged. This goes well beyond what annotations alone provide.

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 dense but front-loaded: purpose, supported examples, return shape, error handling, alternative, and pricing follow in order. Every sentence carries operational information, and there is no filler or repetition.

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 complex, open-world tool with no output schema and six parameters, the description supplies the return structure, status semantics, failure behavior, cost model, and sibling routing. It gives the agent everything needed to decide whether and how to call it.

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 the baseline is 3. The description reinforces that provider and type are detected from the URL, but it does not add parameter-level meaning beyond the schema, nor does it discuss country, transcript, or sandboxing options.

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 opens with a specific verb and resource: 'Get structured JSON for a public page on a supported site from its normal URL.' It enumerates supported providers and page types, and explicitly names the sibling for unsupported sites ('use webscraping_ai_fields'), making it easy to distinguish from alternatives.

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?

It states the condition for use (supported site, normal URL) and gives an explicit alternative for other sites: 'For other sites, use webscraping_ai_fields.' It also explains what happens for unsupported URLs (400 error, not charged, message lists support), which tells the agent when the tool will not work.

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