Skip to main content
Glama

adb_revoke_permission

Revoke a runtime permission from an Android package to reset permission state, enabling first-run flow testing and denial-handling validation.

Instructions

Revoke a runtime permission from a package. Useful for resetting permission state to test first-run flows or denial handling.

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": {
      "packageName": "<packageName>",
      "permission": "<permission>"
    },
    "name": "adb_revoke_permission"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
permissionYesFull permission string (e.g., 'android.permission.CAMERA')
packageNameYesPackage name (e.g., 'com.example.app')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden for a mutating tool. It never says whether root or a debuggable build is required, whether the target app must be stopped, whether the change takes effect immediately, or what happens if the permission was not previously granted.

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 sentences, the action first and the rationale second, with no filler. Nothing is repeated from the name or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter mutation with no annotations and no output schema, the description covers what and why but omits prerequisites and post-conditions. An agent knows what the call does but not what it needs in order to succeed.

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 the three parameters are already documented with examples. The only added meaning is the word 'runtime', which implies only dangerous permissions are valid targets — a small but real refinement over the schema's generic 'Full permission string'.

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?

States a specific verb and resource: 'Revoke a runtime permission from a package.' An agent can immediately tell this is the inverse of adb_grant_permission, though the description never names that sibling or adb_list_permissions/ adb_permission_audit explicitly.

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?

Supplies a concrete use case ('resetting permission state to test first-run flows or denial handling'), which tells the agent when this is the right call rather than adb_clear_data or a manual settings change. It stops short of naming alternatives or exclusions.

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

Deploy Server

Other Tools