fetch_parsedFetch a web page through the ScrapeUnblocker API (https://developers.scrapeunblocker.com) and return AI-parsed structured JSON instead of raw HTML (product details, article content, listings).
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The absolute URL to fetch and parse. | |
| proxy_country | No | Optional ISO country code, e.g. 'US'. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true and openWorldHint=true. Description adds that it uses the ScrapeUnblocker API and returns AI-parsed JSON with examples, but does not disclose rate limits, authentication needs, or potential failure modes. With annotations covering safety profile, the description adds moderate context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence is concise, front-loaded with the core action and output format, and every part earns its place with no redundancy or fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has two parameters, no output schema, and annotations providing safety context, the description adequately covers its purpose and output type with examples. It does not explain error handling or output shape detail, but this is acceptable for the complexity level.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Both parameters have descriptions in the input schema (url and proxy_country) with 100% coverage. The tool description does not add any additional meaning or context to the parameters beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'fetch' and resource 'web page', specifies output as 'AI-parsed structured JSON' with examples (product details, article content, listings), and distinguishes from sibling 'fetch_html' which returns raw HTML.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description indicates when to use this tool (when you want structured data instead of raw HTML) but does not explicitly state when not to use or directly compare to alternatives like 'fetch_html' or 'google_search'. Context is clear but exclusions are missing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool maps to a distinct output type: rendered HTML, parsed JSON, search results, or element selectors. fetch_html and fetch_parsed both fetch a page but explicitly serve different extraction needs, so an agent can reliably tell them apart.
All names use lowercase snake_case and mostly follow an action_target pattern: fetch_html, fetch_parsed, list_elements. google_search breaks the pattern slightly but is still predictable and readable.
Four tools is a compact but well-scoped set for a scraping API wrapper. Each tool exposes a distinct capability and none is redundant.
The set covers the core scraping lifecycle: rendering HTML, getting structured data, searching Google, and discovering selectors for interaction. Combined with the steps parameter on fetch_html, agents can navigate, interact, and extract without major gaps.