Skip to main content
Glama

doubao_accounts

List, switch, or remove logged-in Doubao accounts to manage multi-account sessions for image generation. Use it to choose which account handles the next request.

Instructions

查看/切换/移除已登录的豆包账号。

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": "doubao_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoswitch 或 remove 时要操作的账号名
actionNolist(默认) / switch / remove

Output Schema

NameRequiredDescriptionDefault
activeYes
waitingYes
accountsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full behavioral burden. It reveals nothing about the destructive 'remove' action (reversibility, confirmation, effect on the active account), nor about auth requirements or side effects of 'switch'. Naming 'remove' is the only behavioral signal, and that is already implied by the verb.

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?

A single front-loaded sentence with zero filler that covers all three operations. It is efficient, though its brevity is part of why behavioral and usage detail is absent.

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 tool is simple (2 optional params, full schema coverage, output schema present so return values need not be described), and the description covers the operations. However, for a tool that can irreversibly remove an account with no annotations to fall back on, the missing disclosure of destructive behavior and preconditions leaves a real gap.

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 100%: the schema already documents 'name' as the account targeted by switch/remove and 'action' as list(default)/switch/remove. The description adds no syntax, format, or edge-case meaning beyond those fields, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names three concrete operations (view/switch/remove) on a specific resource (already-logged-in Doubao accounts), so an agent can tell what it does. The qualifier '已登录' implicitly separates it from doubao_login, but no sibling is named explicitly, so differentiation is left to inference.

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

Usage Guidelines3/5

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

Usage is only implied: '已登录' suggests accounts must already exist, which is a useful precondition, but the description never says when to use this versus doubao_login or doubao_verify, nor when each of the three actions is appropriate. The schema's action parameter carries the list/switch/remove distinction, not the description.

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