Batch-add up to 50 bookmarks to a specified folder. Validates remaining capacity before insertion to prevent quota overflow.
批量添加多个书签到指定文件夹。单次最多 50 条。执行前会自动严格校验剩余容量，容量不足时提前拦截保护。
| Name | Required | Description | Default |
|---|---|---|---|
| bookmarks | Yes | 书签对象数组，最多 50 条 | |
| folder_id | Yes | 目标文件夹 ID (必须指定具体文件夹，批量添加不支持暂存箱) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses the 50-item batch limit and automatic capacity pre-validation, but it does not cover failure semantics, duplicate handling, permission/auth needs, or whether the operation is atomic.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three compact sentences: purpose first, then batch limit, then capacity-check behavior. Every sentence adds useful information without repetition or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The schema is rich enough for parameters, and the description covers purpose and capacity validation. However, for a batch mutation tool with no annotations and no output schema, it omits important context such as partial-failure behavior and what happens to the created bookmarks.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 100% description coverage, so both parameters are already well documented. The description adds only the batch limit and the requirement for a specific folder, not additional syntax or per-field meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: batch-adding multiple bookmarks to a specified folder. It also clearly distinguishes this from single-bookmark creation through '批量' and '多个书签', and the 50-item limit adds useful scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is for creating multiple bookmarks at once and notes the 50-item cap, but it does not explicitly say when to use this instead of ilinks_create_bookmark or when not to use it. Usage is inferable but not fully guided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.