Skip to main content
Glama
Sign In
Google Play Console MCP

Google Play Console MCP

by abd3lraouf-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Activate Base Plan

activate_base_plan

Activate a subscription base plan to make it available for new subscribers. Specify package name, product ID, and base plan ID to enable.

Instructions

Activate a subscription base plan, making it available to new subscribers.

Disabled in read-only mode.

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": {
      "package_name": "<package_name>",
      "product_id": "<product_id>",
      "base_plan_id": "<base_plan_id>"
    },
    "name": "activate_base_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesParent subscription product ID
base_plan_idYesBase plan ID to activate
package_nameYesApp package name

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses a meaningful effect (availability to new subscribers) and the read-only mode restriction, but it does not mention reversibility, prerequisites, or side effects on existing plans. Adequate but with clear gaps.

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 the core purpose front-loaded and the operational caveat placed after. Every sentence earns its place, and there is no filler.

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 required parameters are fully documented and an output schema exists, so constructing a valid call is straightforward. However, for a lifecycle mutation with no annotations, the lack of details about idempotency, reversibility, and prerequisites leaves meaningful context gaps.

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?

The input schema covers all three parameters with clear descriptions, and the description adds no parameter-level detail. With 100% schema description coverage, the baseline of 3 is appropriate.

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 names a specific action ('Activate') and target resource ('subscription base plan'), and specifies the outcome ('making it available to new subscribers'). This clearly distinguishes it from sibling lifecycle actions like deactivate_base_plan and delete_base_plan.

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?

The description provides clear context: activation is used when a base plan should become available to new subscribers. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of the top score.

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