Skip to main content
Glama

apple_set_price

Replace an app's complete manual price schedule. Retrieve current pricing first, then submit all existing and future entries to preserve so no scheduled prices are lost.

Instructions

Replace the complete manual app price schedule. Call apple_get_pricing first and include every current and future manual price entry that must be preserved.

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": {
      "appId": "<appId>",
      "baseTerritoryId": "<baseTerritoryId>",
      "manualPrices": "<manualPrices>"
    },
    "name": "apple_set_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesApp ID
manualPricesYesComplete desired manual schedule, including existing entries that must remain
baseTerritoryIdYesBase territory ID for that price point, e.g. USA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.0
    • addedInput schema / properties / baseTerritoryId
      Added value: +{
      +  "description": "Base territory ID for that price point, e.g. USA",
      +  "type": "string"
      +}
    • addedInput schema / properties / manualPrices
      Added value: +{
      +  "description": "Complete desired manual schedule, including existing entries that must remain",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "appPricePointId": {
      +        "description": "App Price Point ID returned by apple_list_app_price_points",
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "endDate": {
      +        "anyOf": [
      +          {
      +            "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "End date in YYYY-MM-DD, or null for an open-ended entry"
      +      },
      +      "startDate": {
      +        "anyOf": [
      +          {
      +            "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Start date in YYYY-MM-DD, or null for the current entry"
      +      }
      +    },
      +    "required": [
      +      "appPricePointId"
      +    ],
      +    "type": "object"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
    • removedInput schema / properties / priceTierId
      Removed value: -{
      -  "description": "Price tier ID (use \"0\" for free)",
      -  "type": "string"
      -}
    • removedInput schema / properties / startDate
      Removed value: -{
      -  "description": "ISO 8601 start date",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "appId",
      -  "priceTierId"
      -]New value: +[
      +  "appId",
      +  "baseTerritoryId",
      +  "manualPrices"
      +]
  2. First observedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the safety burden and does so well: 'Replace the complete' combined with 'include every ... entry that must be preserved' makes clear that omitted entries are dropped — critical destructive semantics an agent would otherwise miss. It does not mention permission requirements, rate limits, or what the response contains, which keeps it at 4 rather than 5.

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, both essential, with the destructive replace semantics front-loaded before the prerequisite call. No restatement of the name or filler.

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 3-parameter mutation tool with no annotations and no output schema, the description supplies the two things that matter most: whole-schedule replacement and the get-pricing prerequisite. Gaps remain around permissions and result/confirmation behavior, but nothing essential to calling it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description adds genuine meaning by framing manualPrices as a full replacement set rather than a delta, which changes how an agent constructs the array. It doesn't elaborate on baseTerritoryId or appPricePointId beyond the schema, so it stays just above baseline.

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?

States a specific verb (Replace) and a precisely scoped resource (the complete manual app price schedule), distinguishing it from the read-only siblings apple_get_pricing and apple_list_app_price_points. The 'complete ... schedule' wording signals the whole-collection semantics an agent needs to distinguish it from a per-entry update.

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?

Gives an explicit prerequisite workflow: 'Call apple_get_pricing first' and re-include every current and future entry that must be preserved. That is concrete when-to-use guidance for a destructive operation. It stops short of naming when not to use it (e.g., for a single price change vs. full schedule rewrite), but the prerequisite plus preservation instruction covers the main selection risk.

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