Skip to main content
Glama
PhononX

Carbon Voice

by PhononX

list_messages

Read-only

Retrieve voice messages and conversations from Carbon Voice with filtering by date, user, conversation, or workspace. Access presigned URLs for immediate use.

Instructions

List Messages. By default returns latest 20 messages. The maximum allowed range between dates is 183 days (6 months). All presigned URLs returned by this tool are ready to use. Do not parse, modify, or re-encode them—always present or use the URLs exactly as received.If you want to get messages from a specific date range, you can use the "start_date" and "end_date" parameters. If you want to get messages from a specific date, you can use the "date" parameter. If you want to get messages from a specific user, you can use the "user_ids" parameter. If you want to get messages from a specific conversation, you can use the "conversation_id" parameter. If you want to get messages from a specific folder, you can use the "folder_id" parameter. If you want to get messages from a specific workspace, you can use the "workspace_id" parameter. If you want to get messages for a particular language, you can use the "language" parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNoMax number of results per page is: **50**
sort_directionNoThe field used to sort results is **Creation Date**DESC
start_dateNoStart Date range
end_dateNoEnd Date range
workspace_idNoWorkspace ID (optional)
conversation_idNoConversation ID (optional)
languageNoLanguage (optional)
typeNoType (optional)
folder_idNoFolder ID (optional)
user_idsNoUser IDs (optional). List of user IDs to filter messages by. If not provided, all users will be included.

Implementation Reference

  • MCP tool handler for 'list_messages': authenticates using authInfo and delegates to simplifiedApi.listMessages, formats response or error.
      params: ListMessagesParams,
      { authInfo },
    ): Promise<McpToolResponse> => {
      try {
        // Fallback to regular API
        return formatToMCPToolResponse(
          await simplifiedApi.listMessages(
            params,
            setCarbonVoiceAuthHeader(authInfo?.token),
          ),
        );
      } catch (error) {
        logger.error('Error listing messages:', { params, error });
        return formatToMCPToolResponse(error);
      }
    },
  • src/server.ts:88-124 (registration)
    Registers the 'list_messages' MCP tool with description, input schema (listMessagesQueryParams), and annotations.
      'list_messages',
      {
        description:
          'List Messages. By default returns latest 20 messages. The maximum allowed range between dates is 183 days (6 months). ' +
          'All presigned URLs returned by this tool are ready to use. ' +
          'Do not parse, modify, or re-encode them—always present or use the URLs exactly as received.' +
          'If you want to get messages from a specific date range, you can use the "start_date" and "end_date" parameters. ' +
          'If you want to get messages from a specific date, you can use the "date" parameter. ' +
          'If you want to get messages from a specific user, you can use the "user_ids" parameter. ' +
          'If you want to get messages from a specific conversation, you can use the "conversation_id" parameter. ' +
          'If you want to get messages from a specific folder, you can use the "folder_id" parameter. ' +
          'If you want to get messages from a specific workspace, you can use the "workspace_id" parameter. ' +
          'If you want to get messages for a particular language, you can use the "language" parameter. ',
        inputSchema: listMessagesQueryParams.shape,
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
        },
      },
      async (
        params: ListMessagesParams,
        { authInfo },
      ): Promise<McpToolResponse> => {
        try {
          // Fallback to regular API
          return formatToMCPToolResponse(
            await simplifiedApi.listMessages(
              params,
              setCarbonVoiceAuthHeader(authInfo?.token),
            ),
          );
        } catch (error) {
          logger.error('Error listing messages:', { params, error });
          return formatToMCPToolResponse(error);
        }
      },
    );
  • Zod input schema definition for listMessagesQueryParams used in the tool registration.
    export const listMessagesQueryParams = zod.object({
      "page": zod.number().min(1).default(listMessagesQueryPageDefault),
      "size": zod.number().min(1).max(listMessagesQuerySizeMax).default(listMessagesQuerySizeDefault).describe('Max number of results per page is: **50**'),
      "sort_direction": zod.enum(['ASC', 'DESC']).default(listMessagesQuerySortDirectionDefault).describe('The field used to sort results is **Creation Date**'),
      "start_date": zod.string().datetime({}).optional().describe('Start Date range'),
      "end_date": zod.string().datetime({}).optional().describe('End Date range'),
      "workspace_id": zod.string().optional().describe('Workspace ID (optional)'),
      "conversation_id": zod.string().optional().describe('Conversation ID (optional)'),
      "language": zod.string().optional().describe('Language (optional)'),
      "type": zod.enum(['channel', 'prerecorded', 'voicememo', 'stored', 'welcome']).optional().describe('Type (optional)'),
      "folder_id": zod.string().optional().describe('Folder ID (optional)'),
      "user_ids": zod.array(zod.string()).optional().describe('User IDs (optional). List of user IDs to filter messages by. If not provided, all users will be included.')
    })
  • TypeScript type definition for ListMessagesParams used in handler signature.
    export type ListMessagesParams = {
      page?: number;
      /**
       * Max number of results per page is: **50**
       */
      size?: number;
      /**
       * The field used to sort results is **Creation Date**
       */
      sort_direction?: ListMessagesSortDirection;
      /**
       * Start Date range
       */
      start_date?: string;
      /**
       * End Date range
       */
      end_date?: string;
      /**
       * Workspace ID (optional)
       */
      workspace_id?: string;
      /**
       * Conversation ID (optional)
       */
      conversation_id?: string;
      /**
       * Language (optional)
       */
      language?: string;
      /**
       * Type (optional)
       */
      type?: ListMessagesType;
      /**
       * Folder ID (optional)
       */
      folder_id?: string;
      /**
       * User IDs (optional). List of user IDs to filter messages by. If not provided, all users will be included.
       */
      user_ids?: string[];
    };
  • Generated API client helper that performs the actual GET request to /simplified/messages.
    const listMessages = (
      params?: ListMessagesParams,
      options?: SecondParameter<typeof mutator>,
    ) => {
      return mutator<ListMessagesResponse>(
        { url: `/simplified/messages`, method: 'GET', params },
        options,
      );
    };
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds valuable behavioral context beyond annotations: default pagination (latest 20), date range limit (183 days), and critical handling instructions for presigned URLs ('Do not parse, modify, or re-encode them'). It doesn't mention rate limits or authentication needs, but provides useful operational details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly verbose and repetitive with eight consecutive 'If you want...' sentences that duplicate schema information. While front-loaded with important behavioral details, the parameter listing adds unnecessary length without corresponding value. The structure could be significantly streamlined.

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?

Given the tool's complexity (11 parameters) and lack of output schema, the description provides good coverage of key behavioral aspects (pagination defaults, date limits, URL handling). With annotations covering safety and high schema coverage for parameters, the description adds necessary context about operational constraints, though it could better explain the return format.

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?

With 91% schema description coverage, the schema already documents most parameters thoroughly. The description adds minimal semantic value by listing parameter purposes in a repetitive 'If you want...' format, but doesn't provide syntax examples, format details, or constraints beyond what's in the schema. The baseline 3 is appropriate given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as 'List Messages' with specific details about default behavior (latest 20 messages) and date range limitations. It distinguishes from siblings by focusing on listing rather than creating, deleting, or getting specific messages, though it doesn't explicitly name alternatives like 'get_message' or 'get_recent_messages'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides implied usage guidance through parameter explanations (e.g., 'If you want to get messages from a specific date range...'), but lacks explicit when-to-use vs. when-not-to-use statements or named alternatives. It doesn't clarify when to choose this over 'get_recent_messages' or 'get_message' from the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PhononX/cv-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server