app-publish-mcp

apple_update_category

Update an app's primary and secondary category on the App Store by providing the app ID and desired category IDs.

Instructions

Update app primary/secondary category

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": {
      "appInfoId": "<appInfoId>"
    },
    "name": "apple_update_category"
  }
}

Input Schema

Name	Required	Description
`appInfoId`	Yes	AppInfo ID
`primaryCategoryId`	No	Primary category ID (e.g. SOCIAL_NETWORKING)
`secondaryCategoryId`	No	Secondary category ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Mar 19, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. The description merely states 'Update' without indicating whether the operation is destructive, idempotent, or what happens to existing categories if only one parameter is provided. This lacks the necessary transparency for safe invocation.

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?

The description is a single, concise sentence that conveys the core functionality without any extraneous words. It is appropriately front-loaded and efficient.

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?

Given the simplicity of the tool (no output schema, no nested objects, and high schema coverage), the description is minimally adequate. However, it lacks behavioral context such as whether both category IDs are optional or the effect of partial updates, which would improve completeness for an AI agent.

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 provides 100% coverage for all parameters with clear descriptions. The tool description adds no additional meaning beyond what the schema already conveys. Therefore, a baseline score 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 explicitly states the action ('Update') and the resource ('app primary/secondary category'), which is a specific verb+resource combination. It effectively distinguishes the tool from its siblings, as no other sibling tool has a similar purpose.

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 the tool should be used when updating app categories, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., using get_app_info first to check current categories) or mention any prerequisites (e.g., existence of the app).

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

Deploy Server