Skip to main content
Glama
oxylabs

Oxylabs MCP Server

Official

ai_crawler

Read-only

Crawl a website from a starting URL to extract the information you specify. Returns data in markdown, JSON, CSV, or Toon format, with optional JSON schema and JavaScript rendering for structured results.

Instructions

Tool useful for crawling a website from starting url and returning data in a specified format.

Schema is required only if output_format is json, csv or toon. 'render_javascript' is used to render javascript heavy websites. 'return_sources_limit' is used to limit the number of sources to return, for example if you expect results from single source, you can set it to 1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL from which crawling will be started.
schemaNoThe JSON schema to use for structured data extraction from the crawled pages. Only required if output_format is json, csv or toon.
user_promptYesWhat information user wants to extract from the domain.
geo_locationNoTwo letter ISO country code to use for the crawl proxy.
output_formatNoThe format of the output. If json, csv or toon, the schema is required. Markdown returns full text of the page. CSV returns data in CSV format. Toon(Token-Oriented Object Notation) returns data in Toon format, which is optimized for AI agents.markdown
render_javascriptNoWhether to render the HTML of the page using javascript. Much slower, therefore use it only for websites that require javascript to render the page. Unless user asks to use it, first try to crawl the page without it. If results are unsatisfactory, try to use it.
return_sources_limitNoThe maximum number of sources to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations only provide readOnlyHint=true, which the description respects. The description does not add further behavioral details (e.g., no side effects, rate limits, or data retention), but it does not contradict the annotation either. Given the read-only nature is already indicated, the description adds little beyond that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and redundant, repeating parameter details that are already in the schema. For example, the URL and render_javascript explanations are duplicated verbatim. This wastes tokens and reduces clarity.

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

Completeness3/5

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

An output schema is present but the description does not explain the structure or any exceptional behaviors. It briefly mentions returning data in a specified format, but does not elaborate on how the crawl is scoped or what happens with large sites. Given the completeness of the input schema and presence of output schema, the description is adequate but not thorough.

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 tool description adds no new parameter information. The prose repeats the schema definitions without clarifying edge cases or relationships, so it meets the baseline but provides no added value.

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?

The description clearly states the tool crawls a website starting from a URL and returns data in a specified format. However, it does not differentiate from sibling tools like ai_scraper or universal_scraper, which might also crawl pages.

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

Usage Guidelines2/5

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

The description does not explicitly state when to use this tool over alternatives. It implies output format flexibility but lacks guidance on scenarios favoring ai_crawler over other scrapers or search tools.

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/oxylabs/oxylabs-mcp'

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