Huawei App Gallery

get_install_failure_report_url

Obtain a download URL for an installation failure report in CSV or Excel format over a date range up to 180 days. Identify and analyze app installation issues.

Instructions

Get download URL for installation failure report (CSV or Excel). Max 180-day range.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "language": "<language>",
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "get_install_failure_report_url"
  }
}

Input Schema

Name	Required	Description
`app_id`	No	AppGallery Connect app ID. Optional if HUAWEI_APP_ID is set in the environment.
`language`	Yes	Column header language.
`start_time`	Yes	YYYYMMDD (UTC).
`end_time`	Yes	YYYYMMDD (UTC).
`group_by`	No	date (default), deviceName, downloadType, appVersion, or countryId.
`export_type`	No	Default: CSV.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Mar 24, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It only states the action is a 'get' (read), but lacks details on authorization, rate limits, or any side effects. Minimal behavioral disclosure.

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?

Two sentences, front-loaded with the core purpose. Efficient and to the point. Slight improvement could be more structured, but overall concise.

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?

Given no output schema, description implies it returns a URL. It covers the key constraints (format, date range). Could explicitly state return type, but sufficient for a simple URL retrieval tool.

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 covers all 6 parameters with descriptions (100% coverage). The description adds only the context of CSV/Excel formats, which is already in the schema enum. No additional parameter semantics beyond schema.

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?

Description clearly states verb 'get', resource 'installation failure report', and format options (CSV or Excel). It also adds a time range constraint. This distinguishes it from the sibling 'get_download_report_url' tool.

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 explicit guidance on when to use this tool versus alternatives. The description mentions a max 180-day range but does not outline prerequisites, common scenarios, or when to avoid using it.

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

Deploy Server