Skip to main content
Glama
thenavidm

fal.ai MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update storage settings

update_storage_settings
Destructive

Set account-level storage lifecycle rules for newly uploaded fal CDN files, including expiration and default ACL access. Null fields reset to system defaults.

Instructions

Replaces the account-level storage lifecycle settings applied to newly uploaded fal CDN files. Omitted or null fields are cleared (reset to the system default), so always send the full desired configuration.

ACL rules referencing users that do not exist are dropped. The response reflects the settings actually saved, so verify it contains the rules you sent.

These are the same settings that the per-request X-Fal-Object-Lifecycle-Preference header overrides on individual requests.

Authentication: Required. The API key must have the account:settings:write permission.

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.
initial_aclNo
payload_fileNoAbsolute regular non-symlink private JSON file, at most 1 MiB. Cannot mix with other body inputs.
expiration_duration_secondsNoSeconds after which newly uploaded files automatically expire and are deleted. Null disables auto-expiration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv3.0.1
    • addedInput schema / $defs
      Added value: +{
+  "initial_acl": {
+    "additionalProperties": false,
+    "description": "Default ACL applied to newly uploaded files. Null uses the system default (public).",
+    "properties": {
+      "default": {
+        "description": "Fallback decision when no user-specific rule matches",
+        "enum": [
+          "allow",
+          "forbid",
+          "hide"
+        ],
+        "type": "string"
+      },
+      "rules": {
+        "default": [],
+        "description": "User-specific overrides to the default decision",
+        "items": {
+          "additionalProperties": false,
+          "description": "A per-user access control rule",
+          "properties": {
+            "decision": {
+              "description": "Access decision applied to this user",
+              "enum": [
+                "allow",
+                "forbid",
+                "hide"
+              ],
+              "type": "string"
+            },
+            "user": {
+              "description": "User nickname or user ID the rule applies to",
+              "minLength": 1,
+              "type": "string"
+            }
+          },
+          "required": [
+            "user",
+            "decision"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "default"
+    ],
+    "type": [
+      "object",
+      "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 / initial_acl / $ref
      Added value: +"#/$defs/initial_acl"
    • removedInput schema / properties / initial_acl / additionalProperties
      Removed value: -false
    • removedInput schema / properties / initial_acl / description
      Removed value: -"Default ACL applied to newly uploaded files. Null uses the system default (public)."
    • removedInput schema / properties / initial_acl / properties
      Removed value: -{
-  "default": {
-    "description": "Fallback decision when no user-specific rule matches",
-    "enum": [
-      "allow",
-      "forbid",
-      "hide"
-    ],
-    "type": "string"
-  },
-  "rules": {
-    "default": [],
-    "description": "User-specific overrides to the default decision",
-    "items": {
-      "additionalProperties": false,
-      "description": "A per-user access control rule",
-      "properties": {
-        "decision": {
-          "description": "Access decision applied to this user",
-          "enum": [
-            "allow",
-            "forbid",
-            "hide"
-          ],
-          "type": "string"
-        },
-        "user": {
-          "description": "User nickname or user ID the rule applies to",
-          "minLength": 1,
-          "type": "string"
-        }
-      },
-      "required": [
-        "user",
-        "decision"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-}
    • removedInput schema / properties / initial_acl / required
      Removed value: -[
-  "default"
-]
    • removedInput schema / properties / initial_acl / type
      Removed value: -[
-  "object",
-  "null"
-]
    • addedInput schema / properties / payload / properties / initial_acl / $ref
      Added value: +"#/$defs/initial_acl"
    • removedInput schema / properties / payload / properties / initial_acl / additionalProperties
      Removed value: -false
    • removedInput schema / properties / payload / properties / initial_acl / description
      Removed value: -"Default ACL applied to newly uploaded files. Null uses the system default (public)."
    • removedInput schema / properties / payload / properties / initial_acl / properties
      Removed value: -{
-  "default": {
-    "description": "Fallback decision when no user-specific rule matches",
-    "enum": [
-      "allow",
-      "forbid",
-      "hide"
-    ],
-    "type": "string"
-  },
-  "rules": {
-    "default": [],
-    "description": "User-specific overrides to the default decision",
-    "items": {
-      "additionalProperties": false,
-      "description": "A per-user access control rule",
-      "properties": {
-        "decision": {
-          "description": "Access decision applied to this user",
-          "enum": [
-            "allow",
-            "forbid",
-            "hide"
-          ],
-          "type": "string"
-        },
-        "user": {
-          "description": "User nickname or user ID the rule applies to",
-          "minLength": 1,
-          "type": "string"
-        }
-      },
-      "required": [
-        "user",
-        "decision"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-}
    • removedInput schema / properties / payload / properties / initial_acl / required
      Removed value: -[
-  "default"
-]
    • removedInput schema / properties / payload / properties / initial_acl / type
      Removed value: -[
-  "object",
-  "null"
-]
  2. First observedv2.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint/readOnlyHint/idempotentHint/openWorldHint) by disclosing full-replacement semantics, that null clears to system default, that ACL rules for non-existent users are silently dropped, that the response reflects only what was saved, and the required auth permission account:settings:write.

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-loads the core replace operation, then the destructive null-clearing warning, then edge-case behavior, then the header relationship, then auth. Every sentence carries non-redundant operational information with no filler.

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 destructive, nested-body mutation with no output schema, the description covers the destructive semantics, the required auth scope, and what the response contains. An agent has everything needed to invoke it safely.

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 already 83% (baseline 3), but the description adds meaningful semantics the schema does not: null/omitted fields reset to default, so a full configuration must be sent, and invalid-user ACL rules are dropped on save. These materially change how the caller populates the parameters.

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 (replaces) and resource (account-level storage lifecycle settings applied to newly uploaded fal CDN files), with scope qualifiers ('account-level', 'newly uploaded') that distinguish it from the per-file ACL siblings (set_storage_file_acl, get_storage_file_acl). An agent can tell what it configures without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Gives strong invocation guidance ('always send the full desired configuration' because omitted/null fields are cleared) and explains the relationship to the per-request header. However, it never states when to use this vs alternatives such as get_storage_settings (read) or set_storage_file_acl (per-file), so routing between siblings is left to inference.

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