Fast.io

Share Management

share_manage

Destructive

Fastio shares (write): create, update, archive/unarchive, delete, autotitle (AI-generates and applies a title/description; consumes credits). quickshare-create is deprecated (error 10756); single-file links are fileshare_manage action create. Destructive: delete (permanent). Reads are on share. action='describe' gives the full action/param reference. Enabling Deep Indexing costs credits (10 per page).

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Share title (2-80 chars; maps to API 'title').
`title`	No	Share title (2-80 chars). Alias of name.
`action`	Yes	Operation. Use 'describe' for full action reference.
`expand`	No	quickshare-create only: 'node' adds the full backend payload under `node`.
`invite`	No	Who can invite others (default: owners).
`notify`	No	Notification setting (default: never).
`confirm`	No	delete: the share's custom_name or id.
`expires`	No	Expiration: 'YYYY-MM-DD HH:MM:SS' for create/update; seconds (default 10800, max 604800) for quickshare-create.
`node_id`	No	File node ID (quickshare-create).
`password`	No	Password (only with 'Anyone with the link').
`share_id`	No	Share profile ID or custom name.
`room_goal`	No	REMOVED with Coordination Rooms (2026-08-25); a call that supplies it is refused.
`custom_url`	No	Custom URL name for the share link (10-100 chars), distinct from custom_name. update: "null" clears it.
`expires_at`	No	ISO 8601 datetime for quickshare expiration.
`share_type`	No	New share type.
`custom_name`	No	Custom share URL name (4-80 chars; Unicode letters, digits, hyphens, underscores). On create, omit it to have one auto-generated.
`description`	No	Share description (10-500 chars).
`folder_name`	No	Name for new folder (default: 'Shared Folder').
`accent_color`	No	Accent color as JSON string.
`display_type`	No	Display mode (default: grid).
`storage_mode`	No	Storage mode (default: independent).
`user_context`	No	autotitle only: context to guide the generated title/description.
`workspace_id`	No	Parent workspace ID (create, quickshare-create).
`create_folder`	No	Create a new workspace folder (workspace_folder mode).
`deep_indexing`	No	Deep Indexing (RAG indexing); costs credits (10/page). create: default false; always false on workspace_folder shares. Responses report it as `intelligence`.
`owner_defined`	No	Custom metadata as JSON string.
`access_options`	No	Access level. 'Anyone with the link' not allowed for receive/exchange.
`folder_node_id`	No	Workspace folder node ID (workspace_folder mode).
`describe_action`	No	With action='describe': return one action's params and notes instead of the action index.
`workspace_style`	No	Use workspace styling (default: true).
`background_image`	No	Background image index (0-128, default 0).
`comments_enabled`	No	Enable comments (default: true).
`external_invites`	No	update: this share's external-invite switch; only tightens the organization's policy and cannot be reset to inherit.
`background_color1`	No	Primary background color as JSON string.
`background_color2`	No	Secondary background color as JSON string.
`download_security`	No	Download security: off (default), medium (no guest download), high (block all guest downloads).
`guest_chat_enabled`	No	Enable guest chat (default: false).
`anonymous_uploads_enabled`	No	Allow guests to upload anonymously on public Receive/Exchange shares.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 10, 2026

changedInput schema / properties / custom_name / description

Previous value: -"Custom share URL name (4-80 chars; Unicode letters, digits, hyphens, underscores). Omit to have one auto-generated."New value: +"Custom share URL name (4-80 chars; Unicode letters, digits, hyphens, underscores). On create, omit it to have one auto-generated."

addedInput schema / properties / custom_url

Added value: +{
+  "description": "Custom URL name for the share link (10-100 chars), distinct from custom_name. update: \"null\" clears it.",
+  "maxLength": 100,
+  "type": "string"
+}

changedInput schema / properties / deep_indexing / description

Previous value: -"Enable Deep Indexing (RAG indexing); costs credits (10/page). Default false; forced false on workspace_folder shares. Responses report it as `intelligence`."New value: +"Deep Indexing (RAG indexing); costs credits (10/page). create: default false; always false on workspace_folder shares. Responses report it as `intelligence`."

addedInput schema / properties / external_invites

Added value: +{
+  "description": "update: this share's external-invite switch; only tightens the organization's policy and cannot be reset to inherit.",
+  "enum": [
+    "allowed",
+    "denied"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / deep_indexing

Added value: +{
+  "description": "Enable Deep Indexing (RAG indexing); costs credits (10/page). Default false; forced false on workspace_folder shares. Responses report it as `intelligence`.",
+  "type": "boolean"
+}

removedInput schema / properties / intelligence

Removed value: -{
-  "description": "Enable RAG indexing; costs credits (10/page). Default false; forced false on workspace_folder shares.",
-  "type": "boolean"
-}

AddedOct 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, but the description sharpens it ('Destructive: delete (permanent)') and then adds traits annotations cannot express: credit consumption for autotitle and Deep Indexing (10 per page), plus a deprecated action that fails with a specific error code. That is meaningful cost/behavior context beyond the 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.

Conciseness4/5

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

Five dense sentences cover eight actions, deprecation, cost, and a reference escape hatch with no filler, and the write-scope statement is front-loaded. It is terser than the surface area warrants in a couple of places (e.g. cost mentions appear twice: ai/autotitle and Deep Indexing), but nothing is wasted.

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?

For an 8-action, 38-param tool with no output schema, the definition supplies the essentials: action set, sibling routing, destructive/cost warnings, and a discovery mechanism for per-action detail. It does not characterize response shapes per action, but action='describe' is presented as covering that gap.

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% across 38 params, so the schema already documents formats, defaults, enums and per-action applicability (e.g. expires differs between create and quickshare-create). The description adds almost nothing parameter-level beyond pointing at action='describe', so the baseline 3 for heavily schema-documented tools is correct.

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+resource and enumerated write actions ('Fastio shares (write): create, update, archive/unarchive, delete, autotitle'), which maps directly to the action enum. It also names what it is not (reads are on `share`; single-file links are `fileshare_manage` action create), so an agent can separate it from siblings 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 routes the agent: reads go to `share`, single-file links to `fileshare_manage`, and quickshare-create is deprecated with the exact error code (10756). It also tells the agent to call action='describe' to get the full per-action param reference, which is real when-to-use guidance for a multi-action tool.

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

All Fast.io tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?