Skip to main content
Glama
Sign In

OneStore

by so.onestore
OverviewDiscussionsAdmin

List App Store creative videos

list_creative_assets
Read-onlyIdempotent

Read, live from App Store Connect, the creative videos (product page header, search results) placed on the editable App Store version, else the latest one, per locale: placement state and Apple's processing state of each video. Use it after finalize_asset_upload returned ready false.

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_creative_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes
localeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds meaningful context beyond that: it reads live from App Store Connect, falls back to the latest editable version, and reports both placement state and Apple 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 compact and front-loaded, with the main operation stated first and the usage trigger second. The first sentence is dense with nested scope details, but no sentence is filler.

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 simple read-only two-parameter tool with no output schema, the description adequately explains the data source, fallback version behavior, locale scoping, and returned states. The remaining gap is around parameter defaults and syntax, which weakens completeness but does not make the tool uncallable.

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 compensate for both parameters. It hints at locale filtering with 'per locale' but does not explain locale format, omission/default behavior, or the required appId parameter at all.

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?

The description states a specific verb and resource: reading creative videos from App Store Connect, with scope clarified as product page header and search results, editable version fallback, and per-locale placement/processing state. This is clearly distinguishable from general asset or format listing siblings.

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?

It gives an explicit trigger: use after finalize_asset_upload returned ready false. That is useful context for when to reach for this tool, though it does not name when-not-to-use cases or alternative sibling tools.

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

All OneStore toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources