Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

move_message_to_folder

Destructive

Move a voice memo or prerecorded message into a folder or out to a workspace. Use to file a memo after creation; pass a folder_id or workspace_id to set its new placement.

Instructions

Move a message into a folder, or out to a workspace. USE WHEN: Filing a memo. Only voicememo/prerecorded messages you created can be moved, and the message type must match the folder's type. Pass exactly one of folder_id or workspace_id. USE INSTEAD: move_folder to relocate a whole folder. create_voicememo_message with folder_id to file a memo at creation time instead of moving it after. FIRST: message_id comes from list_messages (field results[].id) — call it first if you don't have one. EXAMPLE: {"message_id":"msg-abc","folder_id":"folder-abc"} RETURNS: The updated message with its new placement. ERROR BAD_REQUEST: The message type is not voicememo/prerecorded, it does not match the destination folder's type, or both/neither destination was given. — Check type via get_message and the folder type via get_folder; they must match. Pass exactly one destination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idNoDestination folder. Pass exactly one of `folder_id` or `workspace_id` — both together, or neither, is rejected.
message_idYesMessage to move. Only `voicememo` and `prerecorded` messages can be moved, you must be the message creator, and the message type must match the destination folder's type (a voicememo cannot go into a prerecorded folder).
workspace_idNoDestination workspace, to take the message out of any folder. Pass exactly one of `folder_id` or `workspace_id` — both together, or neither, is rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.10.0
    • changedInput schema / properties / folder_id / description
      Previous value: -"Folder ID"New value: +"Destination folder. Pass exactly one of `folder_id` or `workspace_id` — both together, or neither, is rejected."
    • changedInput schema / properties / message_id / description
      Previous value: -"Only allowed to add messages of type: voicememo,prerecorded"New value: +"Message to move. Only `voicememo` and `prerecorded` messages can be moved, you must be the message creator, and the message type must match the destination folder's type (a voicememo cannot go into a prerecorded folder)."
    • changedInput schema / properties / workspace_id / description
      Previous value: -"Workspace ID"New value: +"Destination workspace, to take the message out of any folder. Pass exactly one of `folder_id` or `workspace_id` — both together, or neither, is rejected."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations indicate destructiveHint=true, and the description enriches this by detailing the mutation constraints: only certain message types, creator requirement, type matching, and rejection of both/neither destination. It also explains the return value and common error cause with remediation steps. This goes well beyond the annotation, which is appropriate for a destructive action.

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?

The description is well-structured with clear headers (USE WHEN, USE INSTEAD, FIRST, EXAMPLE, RETURNS, ERROR) and every sentence serves a purpose. It is concise despite covering multiple aspects, with no redundancy. The action is front-loaded and the format aids agent parsing.

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 3-parameter mutation tool with no output schema, the description is remarkably complete. It covers prerequisites, how to obtain a required ID, the error condition and how to diagnose it, and the return value. Given the complexity and sibling interactions, nothing essential is missing.

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 100% with detailed parameter descriptions, so the baseline is 3. The description adds an example showing the correct combination and a FIRST note about where message_id comes from (list_messages), which helps clarify the practical semantics of the parameters. This additional context justifies a 4.

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?

The description clearly states the action: moving a message into a folder or out to a workspace. It distinguishes itself from siblings by naming move_folder and create_voicememo_message as alternatives. The specific constraints on message types and destination rules make the purpose unambiguous.

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?

Explicit USE WHEN and USE INSTEAD sections provide clear conditions for this tool vs alternatives. It states when to use (filing a memo), prerequisites (voicememo/prerecorded, creator, type match), and the exactly-one-destination rule. This is exemplary routing 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