scrape_pageFetch a public http/https URL and return its rendered HTML, the links on the page, and page metadata (title/description/OpenGraph/canonical/favicon) — in one render. For clean Markdown use read_url instead. Private/internal hosts are blocked.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The http/https URL to scrape. | |
| formats | No | Which representations to return (default: all three). |
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?
Discloses that it renders the page and returns multiple representations in one render, and blocks private hosts. No annotations provided, so the description carries the burden; it does not mention rate limits or error behavior but covers key traits.
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?
Two concise sentences with the main action and key differentiator front-loaded; no redundant wording.
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 no output schema, the description explains the return content (HTML, links, metadata with specific fields) and notes the single-call behavior, making it sufficient for an agent to understand expected outcomes.
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 describes both parameters (url required, formats optional with enum). The description adds context that all three formats are default and mentions the output types, but does not go beyond the schema's minimal descriptions.
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?
States a specific verb (fetch, return), resource (URL), and outputs (HTML, links, metadata), and distinguishes from read_url for Markdown.
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?
Explicitly names the alternative for clean Markdown (read_url) and discloses the restriction on private/internal hosts.
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.
Most tools have clearly distinct purposes, such as extracting PDF text versus filling forms or rendering URLs to PDF versus screenshots. The only mild overlap is read_url and scrape_page, both fetching a URL, but their outputs are explicitly differentiated as clean Markdown versus raw HTML with metadata.
Names mostly follow a verb_noun pattern like extract_pdf_text, fill_pdf_form, and rotate_pdf. A few conversion tools use 'to' constructions (images_to_pdf, markdown_to_pdf, url_to_pdf) and some pluralize objects (merge_pdfs, select_pages), creating minor inconsistency but no real confusion.
With 15 tools, the set is at the upper edge of the ideal range and every tool serves a distinct, useful function within the PDF and URL processing domain. The count feels justified rather than excessive.
The PDF tooling covers creation from images and Markdown, text extraction, form filling and reading, merging, splitting, rotating, selecting pages, and watermarking. URL handling covers reading as Markdown, scraping raw HTML/metadata, generating PDFs, and taking screenshots, providing well-rounded coverage for the stated domain.