Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Screenshot Build All

screenshot_build_all

Run full screenshot stage: sample image, build, install, capture 32 languages x 6 screens with captions, brand, sync to fastlane/screenshots. Not for single captures or uploading.

Instructions

Run the whole turnkey screenshot step: sample image, build and install, captions, capture 32 languages x 6 screens, brand, sync to fastlane/screenshots.

Use when: the mandatory screenshots stage. Not for: single captures (use screenshot_capture) or uploading (use deliver_screenshots). Long-running. Returns: {ok, locales, screens, dir} or the first failing step.

Input Schema

NameRequiredDescriptionDefault
udidYesSimulator UDID from build_list_simulators, e.g. 'A1B2C3D4-...'.
schemeYesXcode scheme name to build, e.g. 'MyApp'.
app_dirYesAbsolute path to the app project directory (contains app.spec.json), e.g. /Users/me/Apps/MyApp.
localesNoList of locale codes, e.g. ['en-US', 'de-DE']; omit for the default set.
projectYesPath to the .xcodeproj or .xcworkspace to build, e.g. /path/App/App.xcodeproj.
bundle_idYesApp bundle identifier in reverse-DNS form, e.g. com.example.app.
sample_promptYesPrompt describing a sample output of the app (fills Result/Gallery screens).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.5
    • addedInput schema / properties / app_dir / description
      Added value: +"Absolute path to the app project directory (contains app.spec.json), e.g. /Users/me/Apps/MyApp."
    • addedInput schema / properties / bundle_id / description
      Added value: +"App bundle identifier in reverse-DNS form, e.g. com.example.app."
    • addedInput schema / properties / locales / description
      Added value: +"List of locale codes, e.g. ['en-US', 'de-DE']; omit for the default set."
    • addedInput schema / properties / project / description
      Added value: +"Path to the .xcodeproj or .xcworkspace to build, e.g. /path/App/App.xcodeproj."
    • addedInput schema / properties / sample_prompt / description
      Added value: +"Prompt describing a sample output of the app (fills Result/Gallery screens)."
    • addedInput schema / properties / scheme / description
      Added value: +"Xcode scheme name to build, e.g. 'MyApp'."
    • addedInput schema / properties / udid / description
      Added value: +"Simulator UDID from build_list_simulators, e.g. 'A1B2C3D4-...'."
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive operation, so the safety profile is covered. The description adds genuinely new behavioral context: it is 'Long-running' and it short-circuits on 'the first failing step'. It stops short of describing side effects on disk (fastlane/screenshots writes) or any prerequisite setup, which keeps it below 5.

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 action sentence, then clearly labelled Use when / Not for / Long-running / Returns lines. Every clause carries information and nothing is repeated from the schema.

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 complex, mutation-style orchestrator tool, the description covers scope, alternatives, runtime characteristics and a return shape (with an output schema also present). It omits side-effect detail such as which directories get written and whether the stage is resumable after a failing step, which is the only remaining gap.

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% across all 7 parameters with concrete examples (UDID format, path examples, locale list format), so the schema does the heavy lifting. The description adds no parameter-level meaning beyond naming the 32x6 capture scope, which is the expected baseline of 3 when coverage is complete.

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 plus the full scope of the turnkey pipeline: sample image, build and install, captions, capture 32 languages x 6 screens, brand, sync to fastlane/screenshots. An agent can distinguish it from the granular screenshot_* siblings (screenshot_capture, screenshot_brand, screenshot_sync) without opening any 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?

Explicit routing: 'Use when: the mandatory screenshots stage. Not for: single captures (use screenshot_capture) or uploading (use deliver_screenshots).' Names both the condition and the two alternative tools, so the choice between this and its siblings is unambiguous.

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