Huawei App Gallery
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HUAWEI_APP_ID | No | Optional default App ID so you don't have to pass it to every tool call. | |
| HUAWEI_CLIENT_ID | Yes | Huawei Connect API Client ID obtained from AppGallery Connect (Users & Permissions → API key → Connect API). | |
| HUAWEI_CLIENT_SECRET | Yes | Huawei Connect API Client Secret obtained from AppGallery Connect (Users & Permissions → API key → Connect API). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_app_infoA | Query app metadata (name, description, category, content rating) from AppGallery Connect. Optionally scope to a release channel with channel_id=2 for open testing. |
| update_app_infoA | Update app metadata in the AppGallery Connect draft (name, description, category, ratings, support contacts, privacy policy). |
| update_language_infoB | Add or update localized store listing (name, description, release notes) for a language. |
| delete_language_infoB | Remove a localized store listing from the app draft. |
| get_upload_urlB | Get a pre-signed upload URL and authCode for an APK/AAB/asset file. Returns uploadUrl, chunkUploadUrl, authCode. |
| upload_fileA | Upload a file to AppGallery using a pre-signed URL (Step 2 of upload flow). Returns fileDestUrl for use in update_app_file_info. |
| upload_app_fileA | Upload APK/AAB from local disk to AppGallery (get URL → upload, auto-chunked >4 GB → attach to draft). |
| update_app_file_infoA | Attach already-uploaded files to the app draft. Use after get_upload_url + manual upload. |
| submit_appA | Submit app for review/release. Supports full, phased, scheduled, channel releases, and open testing (channel_id=2). Save all info first. |
| change_phased_release_stateB | Proceed, roll back, or stop a phased (grey) release. |
| update_phased_releaseC | Convert phased release to full, or update its schedule/percentage. |
| update_release_timeB | Update scheduled release time. Only valid when app is in Releasing state. |
| set_gms_dependencyA | Declare whether the app depends on GMS (Google Mobile Services). |
| query_compile_statusA | Query AAB compilation status for package IDs returned after upload. |
| get_download_report_urlA | Get download URL for app download/install report (CSV or Excel). Max 180-day range. |
| get_install_failure_report_urlB | Get download URL for installation failure report (CSV or Excel). Max 180-day range. |
| submit_app_with_fileB | Submit app for release using a file hosted on your server (Huawei downloads via HTTPS during review). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Most tools map to distinct resources and actions, but the upload flow has three overlapping tools (upload_file, upload_app_file, update_app_file_info) and submit_app vs submit_app_with_file are easy to confuse. Descriptions help, but an agent could still pick the wrong step in the upload/release workflow.
Naming follows a clear verb_noun snake_case pattern throughout, using query_, update_, delete_, get_, upload_, and submit_ consistently. Minor inconsistencies like query vs get, change_phased_release_state vs update_phased_release, and upload_file vs upload_app_file prevent a perfect score.
At 17 tools, the set is slightly above the ideal 3-15 range but reasonable for an app publishing console covering metadata, localization, upload, release management, and reports. No tool feels completely redundant, though the set is on the heavier side.
The core release workflow is covered: metadata, localization, upload/attach, submission, phased/scheduled releases, and reports. However, there is no way to query current submission/review/release status, list existing localized listings, or see uploaded files, which creates a notable gap for agents managing the full lifecycle.