Fast.io

Brand Assets

asset

Read-only

Brand assets (logos, banners, profile photos) on an org, workspace, share, or user: asset types, list, read an asset's bytes. Writes are on asset_manage.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	Operation. Use 'describe' for full action reference.
`asset_id`	No	Asset ID or name.
`entity_id`	No	Entity ID (optional for user).
`asset_type`	No	Asset type key (e.g. 'logo', 'banner', 'photo').
`entity_type`	No	Entity type.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 3, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "describe",
-  "upload",
-  "delete",
-  "types",
-  "list",
-  "read"
-]New value: +[
+  "describe",
+  "types",
+  "list",
+  "read"
+]

removedInput schema / properties / content

Removed value: -{
-  "description": "Plain text content (e.g. SVG).",
-  "type": "string"
-}

removedInput schema / properties / content_type

Removed value: -{
-  "description": "MIME type (default application/octet-stream).",
-  "type": "string"
-}

changedInput schema / properties / entity_id / description

Previous value: -"Opaque ID of a specific object (file, comment, etc.). Pair with entity_type to disambiguate. Entity ID (optional for user)."New value: +"Entity ID (optional for user)."

removedInput schema / properties / file_base64

Removed value: -{
-  "description": "Base64-encoded binary content.",
-  "type": "string"
-}

removedInput schema / properties / file_name

Removed value: -{
-  "description": "Original file name.",
-  "type": "string"
-}

removedInput schema / properties / metadata

Removed value: -{
-  "description": "Additional metadata as JSON array string.",
-  "type": "string"
-}

Changed1 schema field changedJun 26, 2026

changedInput schema / properties / entity_id / description

Previous value: -"Opaque ID of a specific object (file, comment, worklog entry, etc.). Pair with entity_type to disambiguate. Entity ID (optional for user)."New value: +"Opaque ID of a specific object (file, comment, etc.). Pair with entity_type to disambiguate. Entity ID (optional for user)."

Changed12 schema fields changedMay 5, 2026

changedInput schema / properties / action / description

Previous value: -"Operation to perform"New value: +"Operation. Use 'describe' for full action reference."

changedInput schema / properties / action / enum

Previous value: -[
-  "upload",
-  "delete",
-  "types",
-  "list",
-  "read"
-]New value: +[
+  "describe",
+  "upload",
+  "delete",
+  "types",
+  "list",
+  "read"
+]

changedInput schema / properties / asset_id / description

Previous value: -"Asset ID or name (required for: upload, delete, read if asset_type not provided)"New value: +"Asset ID or name."

changedInput schema / properties / asset_type / description

Previous value: -"Asset type key (e.g. 'logo', 'banner', 'photo') (required for: upload, delete, read if asset_id not provided)"New value: +"Asset type key (e.g. 'logo', 'banner', 'photo')."

changedInput schema / properties / content / description

Previous value: -"Plain text content (e.g. SVG). Use this instead of file_base64 for text-based assets. (used by: upload)"New value: +"Plain text content (e.g. SVG)."

changedInput schema / properties / content_type / description

Previous value: -"MIME type (e.g. image/png). Defaults to application/octet-stream (used by: upload)"New value: +"MIME type (default application/octet-stream)."

changedInput schema / properties / entity_id / description

Previous value: -"Entity ID (not needed for 'types' action or 'user' entity_type when operating on authenticated user) (required for: list, upload, delete, read for non-user entities)"New value: +"Opaque ID of a specific object (file, comment, worklog entry, etc.). Pair with entity_type to disambiguate. Entity ID (optional for user)."

changedInput schema / properties / entity_type / description

Previous value: -"Entity type the asset belongs to"New value: +"Entity type."

changedInput schema / properties / file_base64 / description

Previous value: -"Base64-encoded file content for binary files. Use content for text. (used by: upload)"New value: +"Base64-encoded binary content."

changedInput schema / properties / file_name / description

Previous value: -"Original file name (e.g. logo.png) (used by: upload)"New value: +"Original file name."

changedInput schema / properties / metadata / description

Previous value: -"Additional metadata as JSON array string (used by: upload)"New value: +"Additional metadata as JSON array string."

changedInput schema / required

Previous value: -[
-  "action",
-  "entity_type"
-]New value: +[
+  "action"
+]

First observedApr 15, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that reads return an asset's bytes and that mutations live elsewhere, but says nothing about permission requirements, rate limits, or byte-return size/format.

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?

A single front-loaded sentence: resource, scope, capabilities, then the exclusion. No padding whatsoever.

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 a 5-param read-only tool with full schema coverage and no output schema, the description covers scope, entities, and capabilities adequately. It omits the 'describe' action and any detail on what 'read bytes' returns, but those gaps are minor given the schema enumerates every action.

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 coverage is 100% with per-parameter descriptions and two enums, so the schema does the heavy lifting. The description's enumeration of operations (types, list, read) loosely maps to the action enum but adds no format or syntax detail beyond it. 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 the resource concretely (brand assets: logos, banners, profile photos), the scoping entities (org, workspace, share, user), and the read operations performed (types, list, read bytes). An agent can distinguish this from asset_manage purely from the description.

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?

Explicitly routes writes to the sibling `asset_manage`, which is a clean when-not-to-use rule. It lacks a positive trigger statement ('use this when you need to inspect or retrieve assets'), but the read/write split with the alternative named is clear guidance.

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?