app-publish-mcp

google_create_iap

Create a new in-app product (managed product) for an Android app on Google Play. Define SKU, title, description, price, and status to enable purchases within your app.

Instructions

Create a new in-app product (managed product)

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>",
      "sku": "<sku>",
      "defaultLanguage": "<defaultLanguage>",
      "defaultTitle": "<defaultTitle>",
      "defaultDescription": "<defaultDescription>",
      "defaultPriceCurrencyCode": "<defaultPriceCurrencyCode>",
      "defaultPriceMicros": "<defaultPriceMicros>"
    },
    "name": "google_create_iap"
  }
}

Input Schema

Name	Required	Description	Default
`sku`	Yes	Product SKU (unique identifier)
`status`	No		active
`packageName`	Yes	Android package name
`defaultTitle`	Yes	Default product title
`purchaseType`	No		managedUser
`defaultLanguage`	Yes	Default language (e.g. en-US)
`defaultDescription`	Yes	Default product description
`defaultPriceMicros`	Yes	Price in micros (e.g. 990000 for $0.99)
`defaultPriceCurrencyCode`	Yes	Currency code (e.g. USD)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Mar 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the creation action but omits details about required permissions, whether the product is created in a draft state, or what the response looks like. This is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently conveys the core purpose. While concise, it could be slightly expanded without losing brevity. The front-loading is good.

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

Completeness2/5

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

Given the tool's 9 parameters, no output schema, and no annotations, the description is too minimal. It lacks information on return values, side effects, or validation behavior. A more complete description would clarify expected outcomes and prerequisites.

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 itself describes 78% of parameters (e.g., 'Android package name', 'Product SKU'). The description adds no additional meaning beyond the schema. While the schema covers most parameters, the description could provide context on parameter usage but fails to do so. Baseline 3 is appropriate.

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?

The description clearly states the action ('Create') and the resource ('a new in-app product (managed product)'). It is distinguishable from sibling tools like google_update_iap and google_delete_iap. However, it does not provide additional context to differentiate from other creation tools like google_create_edit.

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 is provided on when to use this tool versus alternatives like google_update_iap or google_create_release. There is no mention of prerequisites, typical use cases, or when not to use it.

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

Deploy Server