Skip to main content
Glama
gbatistuta0

AppFactory

by gbatistuta0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metadata Export

metadata_export
Idempotent

Export apple-metadata.md to fastlane per-locale .txt files after validation. Prepares metadata for deliver_metadata, not App Store Connect upload; refuses while ASO stage incomplete if app_dir is set.

Instructions

Export apple-metadata.md to fastlane/metadata//*.txt after validation.

Use when: preparing metadata for deliver_metadata. With app_dir set, refuses until the ASO stage is complete. Not for: uploading to App Store Connect (use deliver_metadata). Returns: {ok, written: [files], locales} or a gate refusal.

Input Schema

NameRequiredDescriptionDefault
app_dirNoApp directory; when given, export is refused until the ASO stage is complete.
dest_dirYesOutput directory for the per-locale .txt files, e.g. <app>/fastlane/metadata.
source_mdYesPath to apple-metadata.md to export.
privacy_urlNoPublic privacy policy URL written to the metadata files.
support_urlNoPublic support page URL.
primary_categoryNoPrimary App Store category id, e.g. 'PHOTO_AND_VIDEO'.
secondary_categoryNoSecondary App Store category id, e.g. 'PRODUCTIVITY'.

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: +"App directory; when given, export is refused until the ASO stage is complete."
    • addedInput schema / properties / dest_dir / description
      Added value: +"Output directory for the per-locale .txt files, e.g. <app>/fastlane/metadata."
    • addedInput schema / properties / primary_category / description
      Added value: +"Primary App Store category id, e.g. 'PHOTO_AND_VIDEO'."
    • addedInput schema / properties / privacy_url / description
      Added value: +"Public privacy policy URL written to the metadata files."
    • addedInput schema / properties / secondary_category / description
      Added value: +"Secondary App Store category id, e.g. 'PRODUCTIVITY'."
    • addedInput schema / properties / source_md / description
      Added value: +"Path to apple-metadata.md to export."
    • addedInput schema / properties / support_url / description
      Added value: +"Public support page URL."
  2. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-readonly, non-destructive, idempotent, closed-world. The description goes beyond them by disclosing the ASO-stage gate that can cause refusal and the validation step before writing — real behavioral context an agent needs. It stops short of describing failure modes beyond the gate.

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 core action, then structured as Use when / Not for / Returns blocks. Every line earns its place with no filler.

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?

With an output schema present, return-value explanation is optional, yet the description still summarizes the return shape and the gate refusal. Combined with complete param docs and annotations, nothing needed to invoke correctly is missing.

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 all seven parameters are already documented with format hints and examples. The description adds only the app_dir gate semantics, which is already mirrored in the schema; baseline 3 is appropriate.

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 (Export), the exact source (apple-metadata.md) and destination pattern (fastlane/metadata/<locale>/*.txt), plus the validation qualifier. Clearly distinct from deliver_metadata, which it names as the upload counterpart.

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 explicit when-to-use (preparing metadata for deliver_metadata), a conditional gate (app_dir set → refuses until ASO stage complete), and an explicit not-for routing to deliver_metadata. Both the selection condition and the exclusion are stated.

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