Skip to main content
Glama
zinja-coder

Apktool MCP Server

by zinja-coder
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

search_in_files

Search for text patterns in decompiled Android app files using paginated results and file extension filters to find relevant code.

Instructions

Search for patterns in files with pagination and enhanced filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of items to return (0 means use default)
offsetNoStarting offset for pagination
max_resultsNoMaximum total results to collect before pagination
project_dirYesPath to the APKTool project directory
case_sensitiveNoWhether search should be case sensitive
search_patternYesText pattern to search for
file_extensionsNoList of file extensions to search in

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed17 schema fields changedv1.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / case_sensitive
      Added value: +{
+  "default": false,
+  "description": "Whether search should be case sensitive",
+  "type": "boolean"
+}
    • addedInput schema / properties / count
      Added value: +{
+  "default": 0,
+  "description": "Number of items to return (0 means use default)",
+  "type": "integer"
+}
    • addedInput schema / properties / file_extensions / description
      Added value: +"List of file extensions to search in"
    • removedInput schema / properties / file_extensions / title
      Removed value: -"File Extensions"
    • addedInput schema / properties / max_results / description
      Added value: +"Maximum total results to collect before pagination"
    • removedInput schema / properties / max_results / title
      Removed value: -"Max Results"
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Starting offset for pagination",
+  "type": "integer"
+}
    • 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 / search_pattern / description
      Added value: +"Text pattern to search for"
    • removedInput schema / properties / search_pattern / title
      Removed value: -"Search Pattern"
    • removedInput schema / title
      Removed value: -"search_in_filesArguments"
    • 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: -"search_in_filesOutput"
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description should disclose behaviors like non-destructiveness, file access patterns, or performance implications. It only mentions 'pagination' and 'enhanced filtering' without operational details.

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?

Single sentence, no fluff, but lacks structure. Could be more informative while remaining concise.

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 7 parameters and an output schema, the description is too brief. It omits key context like supported pattern types (regex?), search scope (only project_dir?), and default behaviors.

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%, so baseline is 3. Description adds no additional meaning beyond the schema; 'enhanced filtering' is too vague to clarify parameter usage.

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?

Description clearly states verb 'Search' and resource 'patterns in files', and adds context about pagination and enhanced filtering. However, it does not differentiate from sibling tools like 'get_smali_file' or 'analyze_project_structure', which have distinct purposes.

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, nor any exclusions or prerequisites. The description only states what it does without context for selection.

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