Skip to main content
Glama

Rename, Copy, or Delete a Sirv File

sirv_cdn_manage_file
Destructive

Rename, copy, or delete a single file in a connected Sirv account; supply a target path for rename/copy and confirm before deleting.

Instructions

Rename, copy or delete one file in the connected Sirv account. Rename and copy need target_path. Delete removes the file from the Sirv account: ask the user first.

These are files in the Sirv account connected to the workspace, not Studio library assets. For a library asset, use sirv_delete_asset or sirv_bulk_edit_assets.

Studio queues the change and Sirv applies it in the background, a few seconds later. Returns the queued change.

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": {
      "action": "<action>",
      "file_path": "<file_path>"
    },
    "name": "sirv_cdn_manage_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to
actionYesWhat to do with the file
file_pathYesFull path of the file in Sirv, such as /products/hero.jpg
target_pathNoNeeded for rename and copy: the new full path, such as /products/boot-2.jpg

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / action / description
      Added value: +"What to do with the file"
    • changedInput schema / properties / file_path / description
      Previous value: -"Full Sirv file path, such as /products/hero.jpg"New value: +"Full path of the file in Sirv, such as /products/hero.jpg"
    • changedInput schema / properties / orgId / description
      Previous value: -"Organization ID (uses default org if omitted)"New value: +"Workspace id from sirv_list_organizations. Default: the workspace you signed in to"
    • addedInput schema / properties / orgId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • changedInput schema / properties / target_path / description
      Previous value: -"Destination path for rename and copy"New value: +"Needed for rename and copy: the new full path, such as /products/boot-2.jpg"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say destructiveHint=true and non-read-only; the description adds the important behavior the annotations cannot express — that the call is asynchronous, that Studio queues it and Sirv applies it seconds later, and that the return value is the queued change rather than a completed mutation. The confirmation guidance for delete and the 'Credits: free' note are further value beyond structured fields.

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 with the operation and scope, then the destructive-action warning, then sibling disambiguation, then async semantics and cost. Four short blocks, each carrying distinct information with no restated text.

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?

There is no output schema, and the description compensates by stating the return is the queued change and that application is deferred by seconds. For a destructive single-file mutation with full annotation coverage, nothing an agent needs to call it safely appears to be missing.

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 all four parameters including the action enum and orgId default are already documented, which sets the baseline at 3. The description reinforces the target_path dependency for rename/copy but adds no new syntax or format detail beyond the schema.

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?

Opens with a specific verb set and resource: 'Rename, copy or delete one file in the connected Sirv account,' and immediately bounds it to a single file. It then explicitly separates this from library assets by naming the sibling tools to use instead, so an agent can pick it without opening any 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?

Gives an explicit negative case ('not Studio library assets') with named alternatives (sirv_delete_asset, sirv_bulk_edit_assets), plus an operational precondition: 'Delete removes the file... ask the user first.' It also states which actions require target_path, which routes the agent per action.

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