Skip to main content
Glama

Update status in bulk

bulk_update_status
DestructiveIdempotent

Update status for a specific list of items, named one by one in titles (exact titles, case-insensitive, max 250 per call). This tool can ONLY update items it is given by name; there is no way to update a whole library in one call, and no parameter will make one appear. For a library-wide change, fetch the titles first (get_by_status) and update them in explicit batches, telling the user what each batch touches. Returns matched/unmatched counts; unmatched titles need individual update_status calls.

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": {
      "media_type": "<media_type>",
      "status": "<status>",
      "titles": "<titles>"
    },
    "name": "bulk_update_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesNew status, in the words update_status lists for this media type
titlesYesExact titles of the items to update (case-insensitive). Required — the update touches only these items.
media_typeYesType of media

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / 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 / 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. Changed5 schema fields changed
    • removedInput schema / properties / filter
      Removed value: -{
      -  "description": "Which items to update",
      -  "enum": [
      -    "all",
      -    "unrated",
      -    "rated"
      -  ],
      -  "type": "string"
      -}
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga"
      +]
    • changedInput schema / properties / status / description
      Previous value: -"New status"New value: +"New status, in the words update_status lists for this media type"
    • addedInput schema / properties / titles
      Added value: +{
      +  "description": "Exact titles of the items to update (case-insensitive). Required — the update touches only these items.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 250,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "media_type",
      -  "status"
      -]New value: +[
      +  "media_type",
      +  "status",
      +  "titles"
      +]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds non-annotation context that matters: a 250-item cap per call, the matched/unmatched return counts (there is no output schema), and the requirement to fall back to single updates for misses. It stops short of stating what happens to an existing status value or whether a partially-failed batch 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences that put the capability first, then the hard constraint, then the workaround. The clause 'no parameter will make one appear' is slightly redundant with the preceding sentence, but it is defensively placed to prevent a common misuse and costs little.

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

Completeness4/5

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

With no output schema, the description usefully explains the return shape (matched/unmatched counts) and the remediation path for misses, which an agent needs to drive a multi-batch workflow. The remaining gap is failure semantics — whether a batch is all-or-nothing and what a duplicate title in `titles` does — which matters for a destructive bulk mutation.

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%, so titles (exact, case-insensitive, maxItems 250) and status are already fully documented in the schema. The description's contribution is mostly emphasis — that the list must be enumerated and no filtering parameter exists — rather than new syntax or format meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource ('update status') plus the exact scope ('a specific list of items, named one by one in `titles`'). It also distinguishes itself from the single-item sibling by noting that unmatched titles need individual update_status calls, so an agent can pick between the two without opening a schema.

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?

Explicitly covers the when-not case ('no way to update a whole library in one call'), names the alternative workflow (fetch titles with get_by_status, then update in explicit batches), and names the fallback tool (update_status) for unmatched titles. It even specifies the user-facing behavior expected during batching ('telling the user what each batch touches').

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