Skip to main content
Glama
taptap

TapTap Open API MCP Server

Official
by taptap

upload_h5_game

Upload a confirmed H5 game to TapTap. Requires a selected app and relative path from the preparation step.

Instructions

    [H5 Game Upload Workflow - Step 2]
    Upload the H5 game to TapTap platform after user confirms info from prepare_h5_upload.

    **PREREQUISITE: An app MUST be selected first.**
    This tool reads app info from cache (selected via select_app or create_app).
    If no app is selected, it will return an error guiding user to select one first.
  

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) Use the same path confirmed in prepare_h5_upload step.
Behavior3/5

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

Discloses that the tool reads app info from cache and returns an error if no app is selected. However, it does not describe any potential side effects, idempotency, or whether uploads can overwrite existing ones. Adequate but could be more detailed.

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?

Description is concise with a workflow label, purpose, prerequisite, and error behavior. Information is front-loaded. The parameter details are in the schema, keeping the main description focused.

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?

Covers prerequisite and error handling, but lacks details on return values or post-upload state. Given the simple parameter set, it is moderately complete but could provide more information on the outcome.

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?

Schema coverage is 100%, with detailed parameter descriptions in the schema. The main description only adds context about using the same path from prepare_h5_upload. Baseline score of 3 is appropriate as schema handles the burden.

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?

Clearly states the action (upload), the target (H5 game to TapTap platform), and the workflow context (step 2 after user confirmation). Distinguishes itself from prepare_h5_upload as the subsequent step.

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?

Explicitly states prerequisite: an app must be selected first. Describes error behavior when prerequisite is not met, guiding user to select an app. Provides clear context for when to use the tool.

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