Skip to main content
Glama

navigate_and_scrape

Navigate to a URL and extract content in one operation. Supports text, HTML, markdown, links, images, and screenshots.

Instructions

Navigate to a URL and optionally scrape content in one operation. Auto-creates session if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idNoBrowser session ID to use. If not provided and auto_create_session is true, a new session will be created automatically
urlYesURL to navigate to. Must be a valid HTTP/HTTPS URL
wait_untilNoNavigation wait condition: 'load' waits for all resources, 'domcontentloaded' waits for DOM (faster), 'networkidle' waits for network activity to stopdomcontentloaded
timeoutNoNavigation timeout in milliseconds. Increase for slow-loading pages
extract_textNoWhether to extract text content from the page. Useful for content analysis and AI processing
extract_htmlNoWhether to extract raw HTML content. Useful for detailed page analysis or when text extraction isn't sufficient
extract_sanitized_htmlNoWhether to extract sanitized HTML content with scripts and styles removed. Safer for AI processing
extract_markdownNoWhether to convert page content to markdown format. Clean format for AI analysis
extract_dom_jsonNoWhether to extract DOM structure as navigable JSON with inline styles. Enables AI navigation of page structure
extract_linksNoWhether to extract all links from the page. Returns array of {text, href} objects
extract_imagesNoWhether to extract all images from the page. Returns array of {alt, src} objects
capture_screenshotNoWhether to capture a screenshot of the page and store as base64. Enables AI visual analysis
screenshot_full_pageNoWhether to capture full page screenshot or just viewport. Only used if capture_screenshot is true
auto_index_websiteNoWhether to automatically index this page in the website database for future reference
selectorNoCSS selector to limit extraction to specific elements. If provided, only content within matching elements will be extracted
wait_for_selectorNoCSS selector to wait for before extracting content. Useful for dynamic content that loads after navigation
auto_create_sessionNoWhether to automatically create a new session if session_id is not provided. Convenient for one-off operations
browser_typeNoBrowser engine to use when creating a new session (only used if auto_create_session is true)
Behavior2/5

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

With no annotations provided, the description carries the full burden. It mentions auto-creating sessions but does not disclose side effects, error handling, or other behavioral traits like rate limits or authentication needs.

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 sentences, front-loaded with the core action, and contains no redundant information. Every word adds value.

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?

Given the high parameter count, no output schema, and no annotations, the description is adequate but leaves gaps: it doesn't summarize return values, error scenarios, or contrast with sibling tools like 'scrape_content'.

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%, so parameters are already well-documented. The description adds context about auto-creating sessions but doesn't significantly enhance parameter understanding beyond the schema.

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 the tool navigates to a URL and optionally scrapes content, combining two operations. It distinguishes itself from sibling tools like 'navigate_to_url' and 'scrape_content' by offering a combined operation.

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

Usage Guidelines3/5

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

The description implies the tool is for one-step navigation and scraping, but lacks explicit guidance on when to use it versus the separate navigate/scrape siblings. No exclusion criteria or alternatives are mentioned.

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/ZachHandley/ZMCPTools'

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