Skip to main content
Glama

Bulk Edit Assets

sirv_bulk_edit_assets
Destructive

Apply a single change, such as tagging, moving, copying, deleting, restoring, or favoriting, to up to 500 library assets in one call while skipping assets you cannot modify.

Instructions

Make one change to up to 500 library assets in one call. operation picks the change:

  • favorite, unfavorite: set or clear the favourite flag.

  • addTags, removeTags: add or remove the tags in tagIds. These are tag ids, not tag names.

  • moveToFolder: move the assets to folderId, or to the top level when it is null.

  • copyToFolder: copy the assets to folderId. The originals stay where they are.

  • delete: move the assets to the trash (soft delete).

  • restore: bring assets back from the trash.

Use it for several assets. To change one asset's file name, alt text or metadata, use sirv_update_asset.

Assets that you may not change are skipped and listed in denied. Returns how many assets changed, and the new assets of a copy.

Credits: free.

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": {
      "assetIds": "<assetIds>",
      "operation": "<operation>"
    },
    "name": "sirv_bulk_edit_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to
tagIdsNoTag ids, not names. Needed for addTags and removeTags
assetIdsYesIds of the assets to change, 1 to 500
folderIdNoDestination folder id for moveToFolder and copyToFolder. null means the top level
operationYesThe change to make to every asset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructive and non-idempotent, but the description adds material context they don't carry: delete is a soft delete into the trash with a matching restore, assets the caller can't change are skipped and reported in `denied`, and the cost is free. It stops short of explaining ordering or partial-failure semantics more deeply, but the key risk of the destructive hint is defused.

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?

Front-loaded lead sentence, then a scannable bullet per enum value, then routing and return-value notes. No filler, and every line carries distinct information.

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?

No output schema is present, and the description compensates by describing what comes back: a count of changed assets, the newly created assets for copyToFolder, and the `denied` list. Parameter and return behavior are both covered for a five-parameter 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% and the schema already says tagIds are ids not names, folderId null means top level, and assetIds are 1 to 500. The description restates those facts rather than adding new meaning, so it earns the baseline 3 rather than more.

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?

Specific verb (bulk edit) plus resource (assets) with an explicit cap of 500, and the eight operations are enumerated with one-line semantics each. It also contrasts itself against sirv_update_asset for single-asset edits, so an agent can route without opening either 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?

"Use it for several assets. To change one asset's file name, alt text or metadata, use sirv_update_asset." states both the condition for this tool and the named alternative for the excluded case. The per-operation bullets further tell the agent which `operation` value matches which intent.

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