Skip to main content
Glama
taptap

TapTap Open API MCP Server

Official
by taptap

check_ads_status

Check whether ads SDK is activated for your app and cache the ad space ID. Returns activation status, space ID, and guidance URL if activation is needed.

Instructions

[Step 2 of Ads Workflow] Check ads SDK activation status and cache ad space ID.

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, guide user through app selection process.

When to call this tool:

  • First time: when no ads status exists in local cache

  • Refresh: when user explicitly asks to re-check status (e.g. after activating ads in developer console)

DO NOT auto-poll - only call when user requests or when no cached status exists.

This tool queries the server, updates local cache, and returns:

  • Business status: 0=未开通 | 1=已生效 | 2=账号已被封禁

  • Ad space ID (space_id) - cached when status is "已生效"

  • Guidance URL for activation (if needed)

CRITICAL - Dual condition for proceeding to Step 3: Both conditions MUST be met simultaneously:

  1. Status must be "已生效" (status === 1)

  2. space_id must be valid (non-empty string) If status is 1 but space_id is empty → server-side issue, tell user to retry later.

Status 0: Tell user they can say "重新检查广告状态" to refresh after completing activation. Status 3 (已封禁): DO NOT proceed with any integration steps. Immediately inform user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Since no annotations are provided, the description fully covers behavioral aspects: it queries server, updates local cache, returns status codes, and warns about potential server-side issues. No contradictions.

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 long but well-structured with headings and bullet points. It is front-loaded with step and prerequisite. Some redundancy could be trimmed, but every sentence adds value.

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

Completeness5/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 explains return values (status, space_id, guidance URL) and provides context on how to proceed based on statuses, including edge cases. It is fully complete.

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?

Input schema has 0 parameters, so baseline is 4. The description adds no parameter information, but none is needed. Schema coverage is 100%.

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 identifies the tool as checking ads SDK activation status and caching ad space ID, part of a workflow (Step 2). It distinguishes from sibling tools by specifying its role in the Ads 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?

Provides explicit when to call (first time, user refresh), when not to call (do not auto-poll), and a prerequisite (must have app selected, with alternative tool named). Also gives behavior for different status codes.

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