Skip to main content
Glama

The assets of a website scan

list_website_assets
Read-onlyIdempotent

Asset inventory of a scan: images, style sheets, scripts and fonts with their sizes, findings and state. estimated_bytes is a prediction, optimized_bytes is measured. Scripts and fonts are analysed only. Paged; filter by kind, status, finding or page. Reads only.

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": {
      "scan_id": "<scan_id>"
    },
    "name": "list_website_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
pageNoOnly assets used by this page number.
limitNoDefault 50.
offsetNo
searchNo
statusNo
findingNoFor example modern_format, oversized, heavy, not_lazy, no_srcset, duplicate_content, not_minified.
scan_idYesThe scan's id, from list_website_scans or the web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Reads only' is redundant, but the description adds real behavioral content: the estimated_bytes vs optimized_bytes distinction (prediction vs measured) and the note that scripts and fonts are analysed only, not optimized. Pagination behavior is disclosed; what remains unstated is rate limits or result ordering.

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?

Three short sentences plus a fragment, front-loaded with the resource definition before the estimated/optimized caveat and the filtering note. The only slight waste is 'Reads only,' which merely restates the readOnlyHint annotation.

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

Completeness3/5

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

With eight parameters, no output schema and only 50% schema coverage, the description needs to carry more weight. It covers the returned field group and the paging model, but leaves three parameters (offset, limit, search) undescribed and gives no hint about ordering or what an empty result means.

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 coverage is ~50%: page, limit, finding and scan_id carry inline descriptions, while kind, status, offset and search do not. The description compensates partially by naming kind, status, finding and page as filter dimensions, but offset, limit and search receive no semantic explanation anywhere.

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 first sentence gives a concrete noun-level scope: 'Asset inventory of a scan: images, style sheets, scripts and fonts with their sizes, findings and state,' which tells an agent exactly what resource is returned. It implicitly separates itself from list_website_pages and get_website_report, but never names a sibling or states the boundary explicitly.

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

Usage Guidelines3/5

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

The trailing phrase 'Paged; filter by kind, status, finding or page' hints at how to narrow results, and scan_id ties it to a prior scan fetch. There is no explicit when-to-use versus alternatives (e.g. list_website_pages for page-level data) and no prerequisite that a scan must already exist.

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.

Resources