Skip to main content
Glama
Sign In
appstore-connect-mcp

appstore-connect-mcp

by tomoki013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

[Read] List App Store Connect apps

asc_apps_list

List all apps in your App Store Connect account with their bundle IDs, SKUs, and locales to identify existing apps before taking other actions.

Instructions

Read-only. Lists all apps visible to this App Store Connect account: name, bundle id, SKU, primary locale, and App Store Connect app id. Use this to discover which apps exist before calling other tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "asc_apps_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries full transparency burden. It labels the tool as 'Read-only' and specifies exact output fields, giving a clear behavioral contract. It doesn't discuss pagination or rate limits, but these are less critical for a zero-parameter listing operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences. It front-loads the action and safety label, then lists output fields and usage guidance. Every sentence adds value with no wasted words.

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?

For a simple tool with no parameters and no output schema, the description covers all essentials: what it does, what it returns, and when to use it. This is sufficient for an agent to select and invoke the tool correctly.

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

Parameters4/5

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

The tool has zero parameters, and schema coverage is trivially 100%. The baseline for zero params is 4, and the description adds no parameter-specific semantics because none are needed; it explains what the tool does instead.

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 the specific action ('Lists all apps visible to this App Store Connect account') and enumerates the returned fields (name, bundle id, SKU, primary locale, app id). It clearly distinguishes itself from siblings like asc_app_get by framing this as the discovery step before other tools.

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?

The description explicitly says 'Use this to discover which apps exist before calling other tools,' providing clear when-to-use context. However, it does not mention when not to use it or name alternative tools, so it stops short of a 5.

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

Deploy Server

Other Tools