Skip to main content
Glama

apple_submit_for_review

Initiate the App Store review process for a specific version by providing its version ID.

Instructions

Submit an App Store version for review

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionIdYesApp Store Version ID

Implementation Reference

  • Main handler for apple_submit_for_review. Submits an App Store version for review by POSTing to /appStoreVersionSubmissions with the versionId.
    const submitForReview: ToolDef = {
      name: 'apple_submit_for_review',
      description: 'Submit an App Store version for review',
      schema: z.object({
        versionId: z.string().describe('App Store Version ID'),
      }),
      handler: async (client, args) => {
        return client.request('/appStoreVersionSubmissions', {
          method: 'POST',
          body: {
            data: {
              type: 'appStoreVersionSubmissions',
              relationships: {
                appStoreVersion: {
                  data: { type: 'appStoreVersions', id: args.versionId },
                },
              },
            },
          },
        });
      },
  • Zod schema defining the input: versionId (string) - the App Store Version ID to submit for review.
    schema: z.object({
      versionId: z.string().describe('App Store Version ID'),
  • Tool is exported in the appleTools array (line 1230), which is then registered in src/index.ts (line 59-74) via server.tool().
    export const appleTools: ToolDef[] = [
      // App Management
      listApps, getApp, getAppInfo, updateAppInfoCategory,
      // Bundle IDs
      listBundleIds, createBundleId,
      // Versions & Localizations
      listVersions, createVersion,
      listVersionLocalizations, createVersionLocalization, updateVersionLocalization,
      // App Info Localizations (name, subtitle)
      listAppInfoLocalizations, updateAppInfoLocalization,
      // Screenshots
      listScreenshotSets, createScreenshotSet, uploadScreenshot, deleteScreenshot,
      // Builds
      listBuilds, assignBuild,
      // Age Rating & Review Info
      getAgeRating, updateAgeRating, updateReviewDetail,
      // Submission
      submitForReview, cancelSubmission,
      // Pricing & Availability
      getAppPricing, setAppPrice, listTerritoryAvailability,
      // Customer Reviews
      listCustomerReviews, respondToReview,
      // Bundle ID Capabilities
      listBundleIdCapabilities, enableCapability, disableCapability,
      // Certificates
      listCertificates, createCertificate, revokeCertificate,
      // Provisioning Profiles
      listProfiles, createProfile, deleteProfile,
      // Devices
      listDevices, registerDevice, updateDevice,
      // TestFlight - Beta Groups
      listBetaGroups, createBetaGroup, deleteBetaGroup,
      addBetaTestersToGroup, removeBetaTestersFromGroup,
      // TestFlight - Beta Testers
      listBetaTesters, inviteBetaTester, deleteBetaTester,
      // In-App Purchases
      listIAP, createIAP, getIAP, deleteIAP,
      // Subscription Groups
      listSubscriptionGroups, createSubscriptionGroup, deleteSubscriptionGroup,
    ];
  • ToolDef interface used to define all Apple tools including submitForReview. The handler receives an AppleClient instance.
    interface ToolDef {
      name: string;
      description: string;
      schema: z.ZodObject<any>;
      handler: (client: AppleClient, args: any) => Promise<any>;
    }
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only says 'submit for review' without disclosing that this action is irreversible (once submitted, it goes into review process) or that it may have side effects like triggering notifications. Missing critical context for a submission action.

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?

The description is a single, concise sentence with no unnecessary words. However, for a critical action, brevity comes at the cost of missing important details, but conciseness itself is good.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there is no output schema and no annotations, the description is too minimal. It does not explain what happens after submission, such as the version's state change or possible responses. A submission action warrants more context to be complete.

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 coverage is 100% for the single parameter 'versionId'. The description does not add any additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 clearly states the action (submit) and the resource (App Store version for review). It is specific enough to distinguish from most sibling tools like apple_cancel_submission or apple_list_versions, but lacks additional context about what 'for review' entails.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., version must be in 'Prepare for Submission' state) or that submission is a final step that can be canceled with apple_cancel_submission.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikusnuz/app-publish-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server