Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Website Images Scraper

WebsiteImagesScraper
Read-only

Website Images Scraper: Website Images Scraper is an image scraper API that extracts image URLs and hosting domains from any web page. Send a page URL to retrieve direct image sources, breakdown counts for internal versus external assets, and unique hosting domains. (Cost: 25 credits)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "WebsiteImagesScraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the website you want to scrape images from
maxlinksNoThe limit of image URLs returned from your query
includequeryNoKeep query strings on the scraped image URLs instead of trimming them

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context by disclosing a 25-credit cost and the output shape, including internal/external counts and hosting domains. It does not mention rate limits, authentication, or failure behavior, but with annotations and an output schema present, this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and reasonably short, but it wastes words by repeating the tool name twice at the start: 'Website Images Scraper: Website Images Scraper is...'. The remaining content is useful, but the opening redundancy keeps it from being a clean 4 or 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema and complete parameter documentation, so the description does not need to explain return values in detail. It covers purpose, output highlights, and cost, which is enough for an agent to call it correctly. The main gap is the absence of guidance about when to use it instead of similar scraping siblings.

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 all three parameters are already documented in the input schema. The description reinforces that the input is a page URL and that results are image sources, but it adds no syntax or behavior detail for maxlinks or includequery. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it extracts image URLs and hosting domains from a web page. It also adds useful scope details such as internal versus external asset counts and unique hosting domains. It does not explicitly distinguish itself from nearby siblings like LinkScraper or WebsiteScreenshot, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description explains what the tool does and says to send a page URL, but it gives no explicit when-to-use guidance, no exclusions, and no comparison to alternatives. It does not tell an agent when to choose this over LinkScraper or other website analysis tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All APIVerve toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources