Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_voicememo_message

Create a voice memo from text via text-to-speech or a public audio URL, then file it in a folder or workspace.

Instructions

Create a voice memo, either from text (spoken via text-to-speech) or from an audio file at a URL. USE WHEN: Pass transcript (2-5000 chars) to have Carbon Voice speak the text, or an https audio_url to upload audio, which wins over transcript. File it with folder_id, whose type must match, or a workspace_id. USE INSTEAD: create_conversation_message to post into an existing conversation, or create_direct_message to send to specific people. A voice memo is standalone and lives in a folder or workspace. EXAMPLE: {"transcript":"Reminder to review the pricing deck before Friday."} RETURNS: {message: {id, link, transcript?, audio_url?, duration_ms, status, type, created_at, ...}}. status is often processing at first. ERROR INVALID_AUDIO_URL: audio_url is not https, unreachable, too large, timed out, embeds credentials, or resolves to a private address. — The message gives the reason. Use a public https URL, or pass transcript instead. ERROR BAD_REQUEST: None of transcript, audio_url or links was provided, or the transcript is outside 2-5000 characters. — Provide one of the three, and keep the transcript within the length limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linksNoLink URLs to attach. Max 100, and each must be a valid URL. One of `transcript`, `links` or `audio_url` is required.
audio_urlNoPublic **https** URL to an audio file to upload. Supported formats: .mp3, .m4a, .wav, .aac, .ogg, .flac, .wma, .opus, .webm. Overrides `transcript` when provided. The server fetches this URL, so it must be publicly reachable — private, loopback and link-local addresses are refused, and plain http only works for hosts the operator has allowlisted.
folder_idNoFolder to file the memo in. The folder type must match the memo type.
transcriptNoText to speak via text-to-speech. 2-5000 characters. Ignored when `audio_url` is provided. One of `transcript`, `links` or `audio_url` is required.
workspace_idNoWorkspace to place the memo in when it is not going into a folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.10.0
    • removedInput schema / properties / audio_file
      Removed value: -{
-  "description": "Audio file upload on multipart requests. Supported Formats: .mp3, .m4a, .wav, .aac, .ogg, .flac, .wma, .opus, .webm. (Overwrites transcript)"
-}
    • addedInput schema / properties / audio_url
      Added value: +{
+  "description": "Public **https** URL to an audio file to upload. Supported formats: .mp3, .m4a, .wav, .aac, .ogg, .flac, .wma, .opus, .webm. Overrides `transcript` when provided. The server fetches this URL, so it must be publicly reachable — private, loopback and link-local addresses are refused, and plain http only works for hosts the operator has allowlisted.",
+  "format": "uri",
+  "type": "string"
+}
    • changedInput schema / properties / folder_id / description
      Previous value: -"Folder ID (not allowed when workspace_id specified is different from the folder_id)"New value: +"Folder to file the memo in. The folder type must match the memo type."
    • changedInput schema / properties / links / description
      Previous value: -"Array of links to be attached to the message"New value: +"Link URLs to attach. Max 100, and each must be a valid URL. One of `transcript`, `links` or `audio_url` is required."
    • changedInput schema / properties / transcript / description
      Previous value: -"The Message transcript will be used to generate audio using text-to-speech"New value: +"Text to speak via text-to-speech. 2-5000 characters. Ignored when `audio_url` is provided. One of `transcript`, `links` or `audio_url` is required."
    • changedInput schema / properties / workspace_id / description
      Previous value: -"Workspace ID (not allowed when folder_id specified is different from the folder_id)"New value: +"Workspace to place the memo in when it is not going into a folder."
  2. Changed1 schema field changedv2.8.17
    • addedInput schema / properties / audio_file
      Added value: +{
+  "description": "Audio file upload on multipart requests. Supported Formats: .mp3, .m4a, .wav, .aac, .ogg, .flac, .wma, .opus, .webm. (Overwrites transcript)"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the minimal annotations: audio_url overrides transcript, status is often "processing" at first, and both INVALID_AUDIO_URL and BAD_REQUEST error conditions are fully explained. This gives the agent a reliable model of what happens when the tool is invoked.

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 longer than average but every labeled section (USE WHEN, USE INSTEAD, EXAMPLE, RETURNS, ERRORS) carries useful information. Key selection criteria are front-loaded before return and error details.

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?

Given no output schema, the description compensates with a return shape and the note that status is often 'processing'. It also covers the three mutually exclusive input modes via the BAD_REQUEST error, file destination options, and common failure modes. The schema covers links and formats, so nothing critical is missing for correct invocation.

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 input schema already documents all five parameters well. The description mostly restates schema semantics, such as "audio_url wins over transcript" and the 2-5000 character limit, without adding meaning beyond what the schema already provides.

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 states a specific verb and resource: "Create a voice memo, either from text (spoken via text-to-speech) or from an audio file at a URL." It also differentiates this tool from the sibling tools by explicitly noting that a voice memo is "standalone and lives in a folder or workspace."

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?

The description has explicit USE WHEN guidance for transcript vs audio_url vs folder_id/workspace_id, and a USE INSTEAD section naming create_conversation_message and create_direct_message with the reason. It also gives a concrete example, leaving little 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