Fast.io

Comment Management

comment_manage

Destructive

Fastio comments on files (write): add (with an optional anchor or attachments), edit, delete, bulk-delete, emoji reactions, attach/detach objects. Destructive: delete, bulk-delete. Reads are on comment. action='describe' gives the full action/param reference.

Input Schema

TableJSON Schema

Name	Required	Description
`text`	No	Max 8192 characters; display text (mention markup excluded) max 500, usually the binding limit. CJK and emoji count as one.
`emoji`	No	Single emoji character.
`action`	Yes	Operation. Use 'describe' for full action reference.
`node_id`	No	File node opaque ID.
`share_id`	No	Alias for profile_id; implies profile_type=share.
`reference`	No	Anchor: image region, A/V timestamp, PDF page, or text selection. Max 2048 bytes JSON-encoded (non-ASCII costs 6 each).
`target_id`	No	Object to attach: node, workspace, share, File Share or envelope ID.
`comment_id`	No	Comment opaque ID.
`context_id`	No	Alias for profile_id (either name works)
`profile_id`	No	Workspace, share or File Share ID (pair with profile_type).
`properties`	No	JSON object of app-defined key-values: stored on add, merged on edit (server-managed keys ignored).
`target_ids`	No	Objects to attach (max 25 per comment).
`comment_ids`	No	Comment IDs (max 100).
`context_type`	No	Alias for profile_type (either name works)
`profile_type`	No	Profile type.
`workspace_id`	No	Alias for profile_id; implies profile_type=workspace.
`parent_comment_id`	No	Parent comment ID (reply; one level).

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 10, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "describe",
-  "add",
-  "edit",
-  "delete",
-  "bulk-delete",
-  "reaction-add",
-  "reaction-remove"
-]New value: +[
+  "describe",
+  "add",
+  "edit",
+  "delete",
+  "bulk-delete",
+  "reaction-add",
+  "reaction-remove",
+  "attachment-add",
+  "attachment-detach"
+]

changedInput schema / properties / profile_id / description

Previous value: -"Workspace or share ID (pair with profile_type)."New value: +"Workspace, share or File Share ID (pair with profile_type)."

changedInput schema / properties / profile_type / enum

Previous value: -[
-  "workspace",
-  "share"
-]New value: +[
+  "workspace",
+  "share",
+  "fileshare"
+]

changedInput schema / properties / properties / description

Previous value: -"edit only: JSON object merged into the comment's properties (server-managed keys ignored)."New value: +"JSON object of app-defined key-values: stored on add, merged on edit (server-managed keys ignored)."

addedInput schema / properties / target_id

Added value: +{
+  "description": "Object to attach: node, workspace, share, File Share or envelope ID.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / target_ids

Added value: +{
+  "description": "Objects to attach (max 25 per comment).",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

AddedOct 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description's job is to add detail — and it does, naming exactly which actions are destructive (delete, bulk-delete) rather than leaving the agent to guess across nine actions. It stops short of describing permission requirements, reversibility, or side effects of attachment detach.

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?

Three tightly packed sentences: the write scope first, the destructive warning second, the routing to `comment` and 'describe' last. No filler and every clause carries information the agent needs.

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 17-parameter tool with nested objects and no output schema, the description covers scope, destructiveness, and the read alternative, and delegates exhaustive detail to action='describe'. What is missing is any hint about required identifiers (profile_id/node_id) or what a successful mutation returns, though the describe action mitigates that.

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 the schema already documents all 17 parameters in detail, including the nested anchor object and the region coordinate conventions. The description only alludes to 'optional anchor or attachments' and adds no syntax or constraint detail beyond that, 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+resource ('Fastio comments on files (write)') and then enumerates the exact operations covered: add with anchor/attachments, edit, delete, bulk-delete, reactions, attach/detach. It also distinguishes itself from the sibling read tool `comment`, so an agent can route without opening either 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?

Explicitly routes reads to the `comment` tool and points to action='describe' for the full action/param reference. It does not give per-action when-to-use conditions (e.g. when to prefer bulk-delete over repeated delete), but the write/read split and the describe escape hatch are clear context.

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?