Skip to main content
Glama

scrape_content

Extract text, HTML, links, or images from a browser page using CSS selectors. Waits for dynamic content before extraction.

Instructions

[LEGACY] Scrape content from the current page. Use navigate_and_scrape instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesBrowser session ID to scrape content from. Session must already exist and be on the desired page
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
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_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
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It merely states it scrapes content but does not disclose if it is read-only, destructive, or any side effects. The legacy label hints at deprecation but lacks behavioral details.

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?

The description is very concise (one line plus legacy note) and front-loaded with the legacy warning. It is appropriately sized for a deprecated tool, though it could include a bit more context for agents that might still use it.

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?

With no output schema and no annotations, the description is minimal. It provides the essential directive to use an alternative, but for agents that might still invoke it, it lacks completeness about behavior, return format, or prerequisites beyond the schema.

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 baseline is 3. The description adds no additional parameter meaning beyond what the schema already provides.

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 explicitly states 'Scrape content from the current page' and clearly labels it as '[LEGACY]' with a directive to use navigate_and_scrape instead, distinguishing it from its sibling.

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?

The description gives a clear usage guideline: 'Use navigate_and_scrape instead.' This explicitly tells the agent when not to use this tool and points to the preferred alternative.

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