Skip to main content
Glama
thenavidm

fal.ai MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Move asset collection

move_asset_collection
Destructive

Move a manual asset collection under another collection or to the top level, with five-level nesting and cycle prevention.

Instructions

Move a manual asset collection under another collection, or to the top level. Only manual collections can be moved or act as folders; nesting is limited to 5 levels deep and cannot create a cycle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoExact private account key profile label, not an authenticated provider owner ID.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete native JSON body, mutually exclusive with flat body flags and payload_file. Use schema for union bodies.
payload_fileNoAbsolute regular non-symlink private JSON file, at most 1 MiB. Cannot mix with other body inputs.
collection_idYesCollection ID
Idempotency_KeyNoOptional idempotency key for safe request retries
parent_collection_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv3.0.1
    • addedInput schema / $defs
      Added value: +{
+  "parent_collection_id": {
+    "description": "Parent collection ID to move this collection under, or null to move it to the top level. Must be a manual collection; nesting is limited to 5 levels and cannot create a cycle.",
+    "minLength": 1,
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for the requested mutation, paid work or private output file."New value: +"Set true only when the user asked for exactly this action."
    • addedInput schema / properties / parent_collection_id / $ref
      Added value: +"#/$defs/parent_collection_id"
    • removedInput schema / properties / parent_collection_id / description
      Removed value: -"Parent collection ID to move this collection under, or null to move it to the top level. Must be a manual collection; nesting is limited to 5 levels and cannot create a cycle."
    • removedInput schema / properties / parent_collection_id / minLength
      Removed value: -1
    • removedInput schema / properties / parent_collection_id / type
      Removed value: -[
-  "string",
-  "null"
-]
    • addedInput schema / properties / payload / properties / parent_collection_id / $ref
      Added value: +"#/$defs/parent_collection_id"
    • removedInput schema / properties / payload / properties / parent_collection_id / description
      Removed value: -"Parent collection ID to move this collection under, or null to move it to the top level. Must be a manual collection; nesting is limited to 5 levels and cannot create a cycle."
    • removedInput schema / properties / payload / properties / parent_collection_id / minLength
      Removed value: -1
    • removedInput schema / properties / payload / properties / parent_collection_id / type
      Removed value: -[
-  "string",
-  "null"
-]
  2. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral constraints — that non-manual collections cannot be moved or act as folders, and that the 5-level depth and cycle rules are enforced — which the agent could not infer from annotations alone.

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?

Two sentences with zero filler. The core action and destination are front-loaded, and the constraint sentence immediately follows with no repetition.

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?

No output schema exists, but the mutation semantics and validity rules are covered by the description plus the 86%-covered schema (confirm, idempotency key, payload union). Missing only explicit failure/reversibility behavior, which is a minor gap for a move operation.

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 86%, so the schema already documents collection_id, parent_collection_id (including null = top level), confirm, payload, payload_file, and idempotency key. The description's nesting/cycle detail duplicates the parent_collection_id $defs text rather than extending it, so the baseline 3 applies.

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 ('Move a manual asset collection') plus the destination scope ('under another collection, or to the top level'). This is distinguishable from siblings like update_asset_collection or add_asset_to_collection 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real eligibility constraints for when the move is valid (manual collections only, 5-level nesting cap, no cycles), which is more than most definitions offer. It stops short of naming the alternative sibling (e.g., update_asset_collection) for non-hierarchy edits, so it is clear context rather than full when/when-not guidance.

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

Deploy Server

Other Tools