Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ASC Create App

asc_create_app
Destructive

Creates an app shell in App Store Connect via fastlane produce. Use after a free name is confirmed; requires human approval before writing.

Instructions

Create an app shell in App Store Connect via fastlane produce (live write, needs human approval).

Use when: after aso_check_name confirms a free name; pass candidate_names and the first available is used. Not for: bundle ids (asc_create_bundle_id) or metadata (deliver_metadata). Returns: {ok, app_id, name, ...} or an approval_required refusal.

Input Schema

NameRequiredDescriptionDefault
skuNoUnique SKU string for the app record; omit to derive from the bundle id.
app_nameNoSingle app name; prefer candidate_names. Converted to a one-element candidate list.
bundle_idYesApp bundle identifier in reverse-DNS form, e.g. com.example.app.
approval_idNoApproval id from a previous approval_required refusal; omit on the first call. The human approves out-of-band with `appfactory approve <id>`, then call again with the same arguments and this id.
candidate_namesNoOrdered candidate App Store names; the first one not already taken is used.
primary_languageNoPrimary App Store language, e.g. 'en-US'.en-US

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.5
    • addedInput schema / properties / app_name / description
      Added value: +"Single app name; prefer candidate_names. Converted to a one-element candidate list."
    • addedInput schema / properties / approval_id / description
      Added value: +"Approval id from a previous approval_required refusal; omit on the first call. The human approves out-of-band with `appfactory approve <id>`, then call again with the same arguments and this id."
    • addedInput schema / properties / bundle_id / description
      Added value: +"App bundle identifier in reverse-DNS form, e.g. com.example.app."
    • addedInput schema / properties / candidate_names / description
      Added value: +"Ordered candidate App Store names; the first one not already taken is used."
    • addedInput schema / properties / primary_language / description
      Added value: +"Primary App Store language, e.g. 'en-US'."
    • addedInput schema / properties / sku / description
      Added value: +"Unique SKU string for the app record; omit to derive from the bundle id."
  2. First observedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, but the description adds critical behavior they cannot: this is a live write gated by human approval, the first call may return an approval_required refusal, and a re-call with approval_id is needed. That two-phase approval protocol is genuinely new information.

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?

Front-loaded with the action, then explicit Use when / Not for / Returns sections. Dense and skimmable with no filler sentences; every clause carries routing or behavioral information.

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?

Covers the destructive-write risk, the approval prerequisite, and the refusal outcome well, and an output schema exists so return values need not be detailed further. Minor gap: it doesn't state that the bundle_id must already exist (create_bundle_id ordering), though the 'Not for' clause implies the relationship.

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 description coverage is 100%, so every parameter is already documented in the schema, including candidate_names first-available semantics and approval_id's retry role. The description adds only a restatement ('pass candidate_names and the first available is used'), so the 3 baseline applies.

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?

States a specific verb+resource ('Create an app shell in App Store Connect') and names the underlying mechanism (fastlane produce). The 'Not for' clause explicitly distinguishes it from asc_create_bundle_id and deliver_metadata, so an agent can route without opening another schema.

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

Usage Guidelines5/5

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

Gives an explicit precondition ('after aso_check_name confirms a free name'), the key argument to pass (candidate_names, with first-available semantics), and explicit exclusions naming the sibling tools that cover bundle ids and metadata. Full when/when-not/alternative coverage.

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