Skip to main content
Glama
Sign In
Google Play MCP

Google Play MCP

by fil-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_country_availability

Read which countries a specific app track is available in and check whether its availability syncs with production.

Instructions

Read which countries a track is available in (and whether it syncs with production). Read-only — availability itself is changed in Play Console.

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>",
      "track": "<track>"
    },
    "name": "get_country_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYesTrack name: internal, alpha (closed testing), beta (open testing), production, a custom closed-testing track name, or a form-factor track such as wear:production
editIdNoOptional: read from this open edit (to see uncommitted changes). Without it a temporary edit is opened and deleted.
packageNameYesApplication id (package name), e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description does the important work of declaring read-only status and setting a boundary that mutation happens outside this tool. However, it omits the non-trivial side effect documented only in the schema (a temporary edit is opened and deleted when editId is absent) and says nothing about permissions or auth needs.

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 short sentences with zero filler; the read-only constraint is placed immediately after the purpose, so the front-loaded content is exactly what an agent needs before calling.

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?

For a three-parameter read tool with no output schema and full schema coverage, the description supplies purpose, read-only safety, and the production-sync aspect of the result. The only gap is the edit-lifecycle side effect, which the schema already carries.

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 all three parameters including the editId temporary-edit behavior are already fully documented. The description adds no parameter-level meaning beyond noting that production sync is part of the result, so the baseline 3 applies.

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 ('Read which countries a track is available in') plus the extra dimension of production sync, which is more precise than a bare name restatement. It does not explicitly contrast itself with any named sibling, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

The description implies this is the read path for availability and directs the agent elsewhere for changes ('availability itself is changed in Play Console'), but it names no sibling tool and gives no condition for choosing between reading from an open edit versus a temporary one — that logic lives only in the schema.

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