Skip to main content
Glama

List the images on a web page with absolute URL, alt text, declared width/height

images
Read-only

List the images on a web page with absolute URL, alt text, declared width/height and lazy-loading, plus counts of images missing alt text (accessibility/SEO). Up to 300 images. Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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": "images"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly and openWorld, so the safety profile is covered; the description adds the 300-image ceiling, the 1-3 s latency, and the free-tier quota with per-call pricing above it. Those are real behavioral facts beyond the annotations, though it doesn't say what happens on failure or whether results are truncated silently.

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?

Front-loads the payload fields and the accessibility use case in the first sentence, then handles limits, speed, and pricing compactly after. Three sentences with no filler, though the pricing sentence is the longest and least essential for invocation decisions.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of describing returns and does so explicitly (URL, alt text, width/height, lazy-loading, missing-alt counts), alongside the payment path and result cap. An agent has everything needed to call it and interpret the response.

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 both the url and payment parameters are already fully documented in the schema, including the 'omit on first call' flow. The description adds no syntax or format detail beyond that, so baseline 3 applies.

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?

States a specific verb ('List') and resource ('the images on a web page') and enumerates the returned fields (absolute URL, alt text, declared width/height, lazy-loading) plus the missing-alt-text counts. This clearly separates it from sibling image-adjacent tools such as og_image, favicon, or screenshot without needing to name them.

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

Usage Guidelines4/5

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

Gives clear context for when the tool applies (accessibility/SEO auditing of a page's images) and sets the operating envelope with the 300-image cap and the 1-3 s runtime. It does not name an alternative or state when not to use it, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.