Skip to main content
Glama
zinja-coder

Apktool MCP Server

by zinja-coder
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

build_apk

Build an APK file from a decoded Apktool project, with validation and options for debugging, force rebuild, and custom output path.

Instructions

Build an APK file from a decoded APKTool project with enhanced validation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
debugNoBuild with debugging info
timeoutNoCommand timeout in seconds
force_allNoForce rebuild all files
output_apkNoOptional output APK path
project_dirYesPath to the APKTool project directory

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed15 schema fields changedv1.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / debug / description
      Added value: +"Build with debugging info"
    • removedInput schema / properties / debug / title
      Removed value: -"Debug"
    • addedInput schema / properties / force_all / description
      Added value: +"Force rebuild all files"
    • removedInput schema / properties / force_all / title
      Removed value: -"Force All"
    • addedInput schema / properties / output_apk / description
      Added value: +"Optional output APK path"
    • removedInput schema / properties / output_apk / title
      Removed value: -"Output Apk"
    • addedInput schema / properties / project_dir / description
      Added value: +"Path to the APKTool project directory"
    • removedInput schema / properties / project_dir / title
      Removed value: -"Project Dir"
    • addedInput schema / properties / timeout
      Added value: +{
+  "default": 300,
+  "description": "Command timeout in seconds",
+  "type": "integer"
+}
    • removedInput schema / title
      Removed value: -"build_apkArguments"
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
-  "result": {
-    "additionalProperties": true,
-    "title": "Result",
-    "type": "object"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • removedOutput schema / title
      Removed value: -"build_apkOutput"
  2. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions 'enhanced validation' but does not explain what that entails (e.g., checks, side effects like overwriting existing APK). Lacks information on permissions, required tools (apktool), or potential errors.

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?

Single sentence, no wasted words. Front-loaded with the core action and key qualifier ('enhanced validation').

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?

Despite having an output schema, the description lacks completeness. It does not mention the output location or how validation works. For a build tool with 5 parameters, more context is needed.

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 the schema already documents all 5 parameters. The description adds no additional meaning beyond the schema, meeting the baseline.

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?

The description clearly states the tool builds an APK from a decoded APKTool project, which is distinct from sibling tools like decode_apk (decodes) and clean_project (cleans). The verb 'Build' and resource 'APK file' are specific and unambiguous.

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 such as decode_apk or analyze_project_structure. Lacks prerequisites (e.g., must have a decoded project) or exclusions (e.g., not for building signed APKs).

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/zinja-coder/apktool-mcp-server'

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