Skip to main content
Glama

Add items in bulk

bulk_add_items
Idempotent

Add up to 250 items to the library in ONE call. Use this whenever the user provides a list of more than 3 items to add — never loop add_item. IMPORTANT: always pass year, and pass external_id whenever you know it. Without them each title is resolved by fuzzy text search, which silently picks the wrong version for any ambiguous title (Roma 1972 vs Roma 2018, remakes, reissues). A wrong match is expensive to undo, so resolve ids up front via lookup_item for anything ambiguous rather than adding bare titles. Returns honest counts: {added, skipped_duplicates, failed} plus a per-item result list. Always report the exact counts to the user; never claim success without reading them. Items are added with the default status; to set a different status on what you just added, call bulk_update_status with those exact titles in titles.

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

Input Schema

NameRequiredDescriptionDefault
itemsYesList of items to add (mixed media types allowed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / items / items / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga",
      -  "comic"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic",
      +  "boardgame"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / items / items / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic"
      +]
  3. Changed4 schema fields changed
    • changedInput schema / properties / items / items / properties / external_id / description
      Previous value: -"External database ID for exact matching: ISBN (book), TMDB ID (movie/show), Discogs ID (album), AniList ID (anime)."New value: +"External database ID for exact matching: ISBN (book), TMDB ID (movie), TMDB or TVDB ID (show), Discogs ID (album), AniList ID (anime), IGDB ID (game)."
    • addedInput schema / properties / items / items / properties / format
      Added value: +{
      +  "description": "Games only: physical or digital copy.",
      +  "enum": [
      +    "physical",
      +    "digital"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / items / items / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga"
      +]
    • addedInput schema / properties / items / items / properties / platform
      Added value: +{
      +  "description": "Games only: the platform the user owns it on (e.g. \"PlayStation 5\").",
      +  "type": "string"
      +}
  4. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare the safety profile (not read-only, idempotent, non-destructive), so the description carries the interesting burden and does: it discloses the silent fuzzy-match failure mode, that a wrong match is expensive to undo, and the exact return shape {added, skipped_duplicates, failed} plus a per-item list — valuable since there is no output schema. The instruction to always report exact counts adds a behavioral obligation not captured anywhere in structured fields. It stops short of stating auth requirements, rate limits, or partial-failure atomicity (e.g. whether one bad item aborts the batch).

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?

Front-loaded with the core action and the sibling prohibition, then failure modes, then return handling, then follow-up — a logical order. It is somewhat dense and the wrong-match risk is stated twice ('silently picks the wrong version' and 'a wrong match is expensive to undo'), but nearly every sentence carries actionable guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single array parameter with fully documented nested fields, no output schema, and batch-write semantics, the description covers the decision rule, the disambiguation prerequisite, the failure surface, the return contract, and the default-status behavior with a follow-up path. An agent has everything needed to call it and report results honestly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3; the description earns above that by upgrading 'year' from optional to effectively mandatory and by explaining the consequence of omitting year/external_id (fuzzy resolution, wrong version on ambiguous titles). That is genuine meaning beyond the schema, which merely says year 'helps with disambiguation'.

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?

States a specific verb, resource, and capacity ('Add up to 250 items to the library in ONE call'), and explicitly contrasts itself with the looping alternative 'add_item'. An agent can immediately tell this is the batch-write path rather than the single-item one.

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?

Gives a concrete selection threshold ('whenever the user provides a list of more than 3 items'), a prohibition ('never loop add_item'), a prerequisite step ('resolve ids up front via lookup_item for anything ambiguous'), and a follow-up route ('to set a different status ... call bulk_update_status'). This is explicit when-to-use, when-not, and which sibling to pick instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources