Skip to main content
Glama

List screenshots and icons

list_assets
Read-onlyIdempotent

Read screenshot/icon metadata and variant status. Storage keys are omitted. includeCreativeVideos also reads, live from App Store Connect, the product page header and search result videos placed on the editable App Store version (else the latest one), per locale with their processing state (same as list_creative_assets).

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": {
      "appId": "<appId>"
    },
    "name": "list_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes
cursorNo
includeCreativeVideosNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / includeCreativeVideos
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral details beyond that: storage keys are omitted, and includeCreativeVideos triggers a live App Store Connect read using the editable version or latest version, per locale with processing state.

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 description is front-loaded and compact, with no filler. The third sentence is dense but still earns its place by explaining the optional video-read behavior.

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?

For a three-parameter list tool with no output schema, the description covers the main purpose and the special includeCreativeVideos behavior. However, it leaves pagination via cursor and the role of appId unexplained, so an agent lacks full invocation context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains includeCreativeVideos in useful detail, but appId and cursor are left completely unexplained in both the schema and the description.

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: 'Read screenshot/icon metadata and variant status.' It is clear what the tool returns, but it does not explicitly distinguish itself from siblings like list_creative_assets or list_asset_formats beyond a parenthetical comparison for video processing state.

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?

There is no explicit guidance on when to use this tool versus alternatives such as list_creative_assets or list_asset_formats. The mention of list_creative_assets is only to equate processing-state behavior, not to route the agent between tools.

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