burn-mcp-server

create_collection

Group related bookmarks into new collections to organize saved articles for easier triage and retrieval.

Instructions

Create a new Collection to group related bookmarks together.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Collection name
`bookmark_ids`	No	Initial bookmark UUIDs to include

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.2Aug 6, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations are absent, so the description carries full responsibility. It describes a mutation ('Create') without disclosing side effects, naming constraints, authorization needs, or what happens with duplicate names. The description provides only the basic action and purpose, lacking behavioral depth beyond what is obvious from the tool name.

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, efficient sentence: 'Create a new Collection to group related bookmarks together.' Every word contributes to the core purpose, making it appropriately sized and front-loaded with the action.

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, but the description leaves gaps: it does not mention the optional bookmark_ids parameter (though the schema does), nor does it clarify the return value or creation behavior with duplicate names. For a create operation, this is adequate but not fully complete; the description could have briefly noted optional initial bookmarks or what happens on server response.

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 'name' parameter is described as 'Collection name' and 'bookmark_ids' as 'Initial bookmark UUIDs to include'. The description does not add extra meaning beyond the schema, but it aligns with the purpose. Since the schema handles parameter semantics fully, a baseline score of 3 is appropriate.

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 the action ('Create'), the resource ('a new Collection'), and the purpose ('to group related bookmarks together'). It distinctly differentiates from sibling tools like get_collections (listing) and add_to_collection (modifying existing collections) by explicitly using 'new'.

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?

The description implies usage when a new collection is needed, but it does not explicitly state when to use this tool versus alternatives such as add_to_collection for adding to an existing collection. There is no mention of exclusions or alternative tool names, leaving the guidance implicit.

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