google-play-developer-mcp

apps_list

List every Android app your service account can access using the Play Developer Reporting API's apps.search method.

Instructions

List every Android app the active service account can access. Uses the Play Developer Reporting API's apps.search.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "apps_list"
  }
}

Input Schema

Name	Required	Description	Default
`pageSize`	No
`pageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jun 2, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It states the scope (apps accessible by service account) but omits details about pagination, rate limits, or authentication requirements. The behavior is partially transparent.

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 succinct sentences with no redundancy. Each sentence serves a purpose: stating the action and specifying the underlying API.

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?

The tool is a simple list operation with optional parameters and no output schema. The description covers the high-level purpose but lacks details about response format, pagination behavior, or data fields returned. Given the low complexity, it is minimally complete but leaves gaps.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description provides no explanation for the two parameters (pageSize, pageToken). The schema already shows the parameter names and types, but the description adds no semantic value about their usage or defaults.

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 explicitly states it lists every Android app the active service account can access, distinguishing it from sibling tools like apps_get which retrieves a single app. The mention of the API adds specificity.

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. Sibling tools like accounts_list and reports_apps_search are not compared, and there is no discussion of prerequisites or contexts where this tool should be preferred.

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

Deploy Server