ShapelessAI

List a page's images and videos

list_page_assets

Read-only

The media a page renders (images, videos, logos, the social preview card), largest first, with real pixel sizes and what each is for. fetch_asset the one you want. Free: nothing is charged. Needs the write scope.

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

Input Schema

Name	Required	Description
`url`	Yes	The absolute URL of the page to scan.
`viewport`	No	Which layout to load. Defaults to desktop, which loads the largest imagery.
`budgetUsd`	No	Optional: the most this call may spend, in dollars, default 2, max 10.
`max_assets`	No	How many entries to return (default 40).

Output Schema

Name	Required	Description
`tool`	Yes
`media`	Yes
`output`	No	The tool's own result, shaped by the tool.
`chargedUsd`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover readOnly, openWorld, and non-destructive behavior, while the description adds useful context: largest-first ordering, real pixel sizes, item purpose, a no-charge claim, and a write-scope requirement. The 'Free' statement is somewhat inconsistent with the schema's budgetUsd parameter, so cost behavior is not fully coherent.

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?

The definition is short and front-loads the resource and key return traits before the fetch_asset routing note and auth/cost notes. 'Free: nothing is charged' is redundant and the closing scope note is abrupt, but there is little wasted wording.

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?

For a four-parameter read tool with an output schema and annotations, the description covers what is returned, ordering, cost, auth needs, and the next-step fetch_asset call. It could better distinguish sibling page-inspection tools and reconcile the budget parameter, but it is broadly complete.

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 100%, so the baseline is 3 even without parameter explanation in the description. The description does not clarify url, viewport, max_assets, or budgetUsd semantics, and its 'Free' claim actively conflicts with budgetUsd.

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 names the resource precisely: page media including images, videos, logos, and the social preview card, with largest-first ordering and pixel/purpose details. It also distinguishes the follow-up from fetch_asset, though it does not use an explicit verb like 'list' and does not differentiate from assets_list or probe_media.

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 description implies a workflow: use this tool to see page media, then call fetch_asset for the item you want. It does not state when to choose this over screenshot_page, read_page, assets_list, or probe_media, and it gives no explicit exclusions.

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

All ShapelessAI tools Inspect

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.