Skip to main content
Glama

adb_grep

Search file contents on Android devices by text pattern using fixed-string matching. Supports recursive directory search with depth control and result limits.

Instructions

Search file contents on the device by text pattern. Uses fixed-string matching by default (no regex injection risk). Supports recursive directory search with depth control and result capping. For filename searches, use adb_find instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternYesText pattern to search for
pathYesFile or directory path to search
recursiveNoSearch directories recursively
fixedStringNoUse fixed-string matching (default: true, safer). Set false for regex.
ignoreCaseNoCase-insensitive search (default: true)
maxResultsNoMaximum matching lines to return (1-10000, default 500)
maxDepthNoMaximum directory depth for recursive search (1-50, default 10)
filesWithMatchesNoShow only filenames that contain matches, not the matching lines
rootNoUse root shell for protected paths
deviceNoDevice serial
result_handleNoOptional. If provided, store this tool's result under `result://<tool>/<name>` for retrieval after compaction. Name must be 1-32 chars, [a-zA-Z0-9_-]. Existing handles with the same tool+name are overwritten. Use adb_result_list to see active handles, adb_result_get or the MCP Resource URI to retrieve.
result_handle_ttlNoOptional. TTL in seconds for the result handle (60 to 604800). Default 43200 (12 hours). Ignored if result_handle is not provided.
Behavior4/5

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

Discloses key behaviors: default fixed-string matching (no regex injection), recursive search with depth control, result capping, root option, case-insensitivity, filesWithMatches, and result handle storage. Lacks mention of return format or performance implications, but adequate given no annotations.

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?

Two concise sentences plus one directing to sibling. Front-loaded with purpose and key defaults. No redundant information.

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?

Covers main behaviors and constraints, but lacks explanation of return format (lines of text) and potential performance for large files. Acceptable for a search tool with 12 parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions. The description adds value by highlighting safety (no regex injection default) and summarizing capabilities (recursive, depth, capped).

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?

Clearly states 'Search file contents on the device by text pattern' with verb ('search'), resource ('file contents'), and method ('by text pattern'). Distinguishes from sibling adb_find for filename searches.

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

Usage Guidelines4/5

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

Provides guidance on default fixed-string matching (safer), supports recursion, depth control, and result capping. Explicitly directs to adb_find for filename searches, helping choose the right tool.

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/fullread/DeepADB'

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