post_get_page_sourceFetches and returns page source of provided url. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| proxy_country | No | One of: DE, US, GB, FR, AU, PL, JP, TW. If no country is selected, service will use random proxy. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden for behavioral disclosure. It mentions "Billing per call: 1 Credits," which is useful, but it does not explain proxy behavior, error conditions, whether the returned source is raw HTML, or whether the page is rendered.
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?
The description is two short sentences that front-load the core purpose and then add the cost detail. Every sentence earns its place with no redundancy or filler.
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?
For a simple fetch tool with two parameters and no output schema, the description is minimally viable, but it omits important behavioral context such as response format, proxy selection behavior, and failure modes. The billing note adds value but does not fully compensate for the missing details.
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?
Schema coverage is 50%: proxy_country is fully described, while url only has an example. The description adds no parameter-level meaning beyond restating "provided url," so it neither compensates for gaps nor contradicts the schema.
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?
The description uses a specific verb and resource: "Fetches and returns page source of provided url." This clearly identifies the tool's action and object, and no sibling tools are provided to require differentiation.
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?
The description gives no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The only extra note is billing, which is not usage guidance.
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.
Only one tool exists, so there is no other tool to disambiguate from, but the tool itself is vaguely named ('post_get_page_source') which could be confused with a POST request rather than a fetch. The purpose is clear, but the name adds ambiguity.
The name 'post_get_page_source' mixes 'post' and 'get' which are conflicting HTTP verbs, and 'page_source' is two words in camelCase but not standard convention. It's not part of a pattern since there is only one tool.
A single tool for a server called 'scrapeunblocker' is extremely thin. While it might be a focused utility, a typical scraping server would need more tools for handling different scraping tasks or unblocking mechanisms. The count is far below what would be expected.
The server claims to be an 'unblocker' but only provides a page source fetching tool. There are no tools for handling captchas, proxies, retries, or any other unblocking features as the name suggests. The surface is severely incomplete for the stated purpose.