Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_conversation_message

Post a text or link message into an existing conversation, or reply in a thread by specifying a parent message ID.

Instructions

Post a message into an existing conversation, or reply in a thread. USE WHEN: You have a conversation_id. Pass parent_id (a message ID) to reply as a thread. Either transcript or links is required — the schema marks neither individually, so both param descriptions say so. USE INSTEAD: create_direct_message to reach people who are not already in a conversation. create_voicememo_message for a standalone memo. FIRST: id comes from list_conversations (field results[].id) — call it first if you don't have one. EXAMPLE: {"id":"conv-abc","transcript":"Agreed, shipping Friday."} RETURNS: {message: {id, link, transcript?, status, type, conversation_id, created_at, ...}}. ERROR BAD_REQUEST: Neither transcript nor links was provided. — Pass at least one of them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
linksNoLink URLs to attach. Either `transcript` or `links` is required.
transcriptNoText to speak via text-to-speech. Either `transcript` or `links` is required.
from_message_idNoMessage ID to be used as a base for the new message. (Optional only when from_message_type is NewMessage)
from_message_typeNoFrom Message typeNewMessage

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.10.0
    • changedInput schema / properties / links / description
      Previous value: -"Array of links to be attached to the message"New value: +"Link URLs to attach. Either `transcript` or `links` 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. Either `transcript` or `links` is required."
  2. Changed1 schema field changedv2.8.17
    • changedInput schema / properties / from_message_type / enum
      Previous value: -[
-  "PreRecorded",
-  "NewMessage",
-  "Forward"
-]New value: +[
+  "PreRecorded",
+  "NewMessage",
+  "Forward",
+  "MessageId"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-read, non-destructive operation. The description adds valuable behavioral context: the either/or requirement for transcript/links, the threading behavior via parent_id, the expected return shape, and the specific BAD_REQUEST error condition. It doesn't fully disclose all side effects (e.g., notifications, TTS behavior), but the provided context goes well beyond the annotations.

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 compact and front-loaded. The core action is in the first sentence, followed by clearly labeled USE WHEN, USE INSTEAD, FIRST, EXAMPLE, RETURNS, and ERROR sections. Every sentence earns its place, and the formatting makes it easy for an agent to scan for the key decision points.

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 tool with 5 parameters, no output schema, and moderate complexity, the description covers the essential context: how to get the id, the threading mechanism, the either/or requirement, the return shape, and the primary error case. The from_message_id/from_message_type parameters are not explained in the description, but the schema provides some context. The description is complete enough for an agent to call the tool correctly in the common cases.

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 80%, and the description adds meaning beyond the schema. It clarifies that neither transcript nor links is individually required but at least one must be provided, which the schema descriptions also state but the description reinforces. It explains that parent_id is a message ID for threading, and that id comes from list_conversations. The from_message_id/from_message_type parameters are not explained in the description, but the schema provides some context for them. The description compensates well for the schema's ambiguity around the either/or requirement.

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 opens with a specific verb and resource: 'Post a message into an existing conversation, or reply in a thread.' It clearly distinguishes the tool from siblings by naming create_direct_message and create_voicememo_message as alternatives. The scope is precise: requires an existing conversation_id, and supports either a top-level post or a threaded reply via parent_id.

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 provides explicit USE WHEN, USE INSTEAD, and FIRST guidance. It tells the agent when to use this tool (has a conversation_id), when to use alternatives (create_direct_message for people not in a conversation, create_voicememo_message for standalone memos), and how to obtain the required id (from list_conversations). It also clarifies the parent_id threading behavior and the either/or requirement for transcript/links.

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