Skip to main content
Glama
Sign In
douyin-ide-control

douyin-ide-control

by arusheng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

查询提审 Host 列表

douyin_audit_hosts

Query the official audit host list for a given AppID to obtain valid host options for Douyin mini program and mini game audits.

Instructions

调用官方 tma hosts 查询指定 AppID 可用的审核 Host 列表（douyin_audit 的 host 参数取值参考）。

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>"
    },
    "name": "douyin_audit_hosts"
  }
}

Input Schema

NameRequiredDescriptionDefault
appidYes
timeoutMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are present, so the description carries the full behavioral burden. The word '查询' implies a read-only operation and the phrase '调用官方 tma hosts' gives provenance, but there is no disclosure of return shape, rate limits, timeout behavior, or side effects.

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?

One sentence, front-loaded with the primary action and scope, followed by a compact parenthetical that ties the result to douyin_audit. No unnecessary words.

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 simple two-param query tool, the description clearly states what it queries, for which AppID, and why an agent would call it. It does not give an explicit return format, but 'host列表' sufficiently implies a list, so the remaining gaps are minor.

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 description coverage is 0%, and the description only adds meaning to 'appid' by indicating it selects the available hosts. The optional 'timeoutMs' is not mentioned, so the description only partially compensates for the schema's lack of parameter documentation.

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 uses a specific verb '查询' (query) and a specific resource: the list of available audit hosts for a given AppID. It also states the result is the reference for the 'host' parameter of douyin_audit, which distinguishes it from sibling tools.

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?

It explicitly says the output is the reference for choosing the host parameter when calling douyin_audit, telling an agent when the tool is useful. It does not mention alternatives or exclusions, so it stops short of a 5.

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