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

douyin-ide-control

by arusheng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

构建抖音项目 NPM

douyin_build_npm

Builds npm for Douyin mini programs by selecting the correct command for minigame or miniapp projects, without performing upload or review steps.

Instructions

按工程类型路由：小游戏走 tmg build-npm，其余走 tma build-npm，不执行上传或提审。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "douyin_build_npm"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
projectPathNo
expectedProjectTypeNo

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?

With no annotations, the description must carry the behavioral burden. It does disclose the routing behavior and the non-upload/audit boundary, but it does not disclose side effects such as project file mutations, build output generation, success/failure behavior, or whether a local environment must be prepared.

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 sentence that immediately fronts the routing rule and the exclusion boundary. There is no redundant filler or repetition of the tool name/title.

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?

The core purpose and routing are clear, but the tool has no annotations, no output schema, and three parameter descriptions at 0% coverage. The description does not explain return values, command execution behavior, or the meaning of timeoutMs and projectPath, so an agent still has to infer important invocation details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description needs to explain the parameters. It only indirectly clarifies expectedProjectType through the minigame/others routing. timeoutMs and projectPath are left entirely unexplained, including their purpose, defaults, and whether they are optional at runtime.

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 a specific action (build NPM) and a routing rule based on project type (minigame vs. others). It also explicitly excludes upload and audit, which distinguishes it from sibling tools like douyin_upload and douyin_audit.

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?

It gives explicit routing guidance: minigame projects should use tmg build-npm, others should use tma build-npm. It also states what the tool does not do (upload or audit), helping an agent choose a sibling tool when those actions are needed.

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