NoMac

Manage TestFlight testing

manage_testflight

Destructive

Set test metadata/contact/demo credentials, create/update external groups and public links, invite/remove an explicit tester, submit/distribute a specific Apple build to selected external groups, notify after approval, expire testing, or relay a human-provided encryption answer. Preview without confirm; confirm:true applies. distribute may send to Beta App Review; auto_notify defaults false. Never guess encryption/demo-account attestations. On pending, repeat unchanged arguments with request_key; get_store_operation recovers it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Name of the TestFlight group to create or rename.
`email`	No	Tester's email address, for invite_tester.
`action`	Yes	metadata, create_group, update_group, invite_tester, remove_tester, remove_build, distribute, notify, expire or encryption.
`locale`	No	App Store locale code, for example en-US or de-DE. Defaults to en-US.	en-US
`confirm`	No	false (default) returns a preview and changes nothing. true performs the change; set it only after the user approves that exact preview.
`app_info`	No	Beta app description, feedback email, marketing URL and privacy policy URL.
`group_id`	No	TestFlight group ID from get_testflight, for update_group, invite_tester or remove_tester.
`group_ids`	No	External TestFlight group IDs from get_testflight, for distribute.
`last_name`	No	Tester's last name, for invite_tester.
`tester_id`	No	Apple tester ID from get_testflight, for remove_tester.
`whats_new`	No	What to Test notes shown to testers for this build.
`first_name`	No	Tester's first name, for invite_tester.
`project_id`	Yes	NoMac project ID (prj_…). push_project and connect_status list your projects.
`auto_notify`	No	Notify testers automatically when the build becomes available. Defaults to false.
`request_key`	No	Idempotency key you choose (letters, digits, dash, underscore). Retry a lost response with the same key and identical arguments; use a new key for new work.
`asc_build_id`	No	Apple build ID, from get_testflight.
`review_contact`	No	Contact for Apple's reviewers (name, phone, email) and an optional demo account.
`public_link_limit`	No	Maximum number of testers who can join through the public link (1-10000).
`public_link_enabled`	No	Turn the group's public TestFlight link on or off.
`uses_non_exempt_encryption`	No	The human's answer to Apple's export-compliance question. Never guess.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations cover destructive/openWorld/non-idempotent, but the description adds substantial context beyond them: a two-phase preview/confirm flow, that distribute may trigger Beta App Review, that auto_notify defaults false, and the request_key retry contract. This is genuinely useful behavioral disclosure for a destructive multi-action tool.

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?

It front-loads the action list, then layers the critical procedural rules (preview/confirm, review submission, no guessing, idempotency) in compact sentences. It is dense but appropriate for a 10-action tool; no sentence is wasted.

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?

With annotations declaring the safety profile and an output schema covering returns, the description fills the remaining gaps an agent needs: the preview/confirm gate, the Beta App Review risk, the encryption-attestation rule, and the idempotency recovery path. Complete enough to call correctly.

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 auto_notify's default and confirm's meaning). The description adds action-level semantics but no parameter-level detail beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates concrete operations (set metadata, create/update groups, invite/remove tester, distribute build, expire testing, relay encryption answer) that map cleanly to the action enum, so the agent understands exactly what the tool does. It doesn't explicitly distinguish itself from the read sibling get_testflight, which keeps it from a 5.

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 clear procedural guidance: preview without confirm, confirm:true applies after user approval, never guess encryption/demo attestations, and on a pending result retry with the same request_key while get_store_operation recovers it. It names a sibling for recovery but does not state when to prefer this over get_testflight or set_metadata.

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

All NoMac tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?