Skip to main content
Glama
taptap

TapTap Open API MCP Server

Official
by taptap

prepare_h5_upload

Verify H5 game project directory and confirm app selection to generate upload readiness info.

Instructions

    [H5 Game Upload Workflow - Step 1]
    Use this tool when user wants to publish/upload/deploy H5 game ('发布', '上传', '部署').

    **PREREQUISITE: An app MUST be selected first.**
    Before calling this tool, ALWAYS call get_current_app_info to verify an app is selected.
    If not selected, guide user through:
    1) Call list_developers_and_apps to show available apps
    2) Show list to user and ASK them to choose
    3) Call select_app with user's choice
    4) Then call this tool

    This tool will:
    1. Verify the game project directory (must contain index.html)
    2. Read app info from cache (selected via select_app)
    3. Return confirmation info for user to review

    After gathering info, use upload_h5_game to upload the game.
  

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
genreNoIf user provides a specific game genre, use it directly. If user is unsure or doesn't specify, analyze the code files, game mechanics, UI elements, and gameplay features in the project directory to determine the most appropriate game genre. Available genres keys: rpg, casual, action, strategy, simulation, trivia, arcade, adventure, card, sports, racing, puzzle, educational, music, word, board, and the chinese name of the genre is 角色扮演, 休闲, 动作, 策略, 模拟, 益智, 街机, 冒险, 卡牌, 体育, 竞速, 知识问答, 教育, 音乐, 文字, 桌面和棋类. When analyzing, consider game rules, player interactions, visual elements, and core gameplay loops. If still uncertain after analysis, default to 'casual' as fallback.
gamePathNo**MUST be a relative path** to the H5 game build output directory. ✅ Correct: "dist", "build", "output", "." ❌ Wrong: "/workspace/dist", "/tmp/build" (absolute paths not allowed) **BEHAVIOR:** - If user specifies directory, pass that relative path - If user doesn't specify, ASK: "请问游戏构建产物在哪个目录?(如 dist、build)" - If index.html is in project root, pass "." or leave empty - DO NOT guess - confirm with user if unsure
Behavior4/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 clearly lists the internal steps: verifying the game project directory, reading app info from cache, and returning confirmation info. It does not mention auth requirements or rate limits, but it is transparent enough for a preparatory step.

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 well-structured with sections, but it is somewhat verbose, particularly in the prerequisite explanation. However, every sentence adds value, and the structure aids clarity.

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?

Given no output schema, the description mentions that it returns 'confirmation info for user to review', but does not detail what that includes. However, it covers the workflow, prerequisites, and next steps adequately for a preparatory tool among many siblings.

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%, but the description adds significant value beyond the schema. For genre, it explains how to determine the genre if not specified, including analysis of game files. For gamePath, it clarifies the relative path requirement and provides example correct and wrong paths.

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 clearly states it is Step 1 of the H5 game upload workflow, used when the user wants to publish/upload/deploy H5 games. It distinguishes itself from sibling tools like upload_h5_game and others by specifying its role in the workflow.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool, the prerequisite of having an app selected, and provides a clear step-by-step process for handling the case when no app is selected. It also mentions the next tool to call (upload_h5_game) after gathering info.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taptap/instant-games-open-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server