Skip to main content
Glama
MakingChatbots

Genesys Cloud MCP Server

conversation_topics

Retrieves business-level intents like cancellation or billing detected from speech and text analytics for a specific conversation.

Instructions

Retrieves Speech and Text Analytics topics detected for a specific conversation. Topics represent business-level intents (e.g. cancellation, billing enquiry) inferred from recognised phrases in the customer-agent interaction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conversationIdYesA UUID for a conversation. (e.g., 00000000-0000-0000-0000-000000000000)

Implementation Reference

  • The main handler function for the conversation_topics tool. It receives a conversationId, fetches conversation details via analyticsApi, queries transcript aggregates to find topic IDs, then retrieves topic names from speechTextAnalyticsApi, returning them as JSON.
    export const conversationTopics: ToolFactory<
      ToolDependencies,
      typeof paramsSchema
    > = ({ speechTextAnalyticsApi, analyticsApi }) =>
      createTool({
        schema: {
          name: "conversation_topics",
          annotations: { title: "Conversation Topics" },
          description:
            "Retrieves Speech and Text Analytics topics detected for a specific conversation. Topics represent business-level intents (e.g. cancellation, billing enquiry) inferred from recognised phrases in the customer-agent interaction.",
          paramsSchema,
        },
        call: async ({ conversationId }) => {
          let conversationDetails: Models.AnalyticsConversationWithoutAttributes;
    
          try {
            conversationDetails =
              await analyticsApi.getAnalyticsConversationDetails(conversationId);
          } catch (error: unknown) {
            const errorMessage = isUnauthorisedError(error)
              ? "Failed to retrieve conversation topics: Unauthorised access. Please check API credentials or permissions"
              : `Failed to retrieve conversation topics: ${error instanceof Error ? error.message : JSON.stringify(error)}`;
    
            return errorResult(errorMessage);
          }
    
          if (
            !conversationDetails.conversationStart ||
            !conversationDetails.conversationEnd
          ) {
            return errorResult(
              "Unable to find conversation Start and End date needed for retrieving topics",
            );
          }
    
          // Widen the time range either side to ensure the conversation timeframe is enclosed.
          // Conversation not returned if either only partially covered by interval, or matched exactly.
          const startDate = new Date(conversationDetails.conversationStart);
          startDate.setMinutes(startDate.getMinutes() - 10);
    
          const endDate = new Date(conversationDetails.conversationEnd);
          endDate.setMinutes(endDate.getMinutes() + 10);
    
          let jobDetails: Models.TranscriptAggregateQueryResponse;
          try {
            jobDetails = await analyticsApi.postAnalyticsTranscriptsAggregatesQuery(
              {
                interval: `${startDate.toISOString()}/${endDate.toISOString()}`,
                filter: {
                  type: "and",
                  predicates: [
                    {
                      dimension: "conversationId",
                      value: conversationId,
                    },
                    {
                      dimension: "resultsBy",
                      value: "communication",
                    },
                  ],
                },
                groupBy: ["topicId"],
                metrics: ["nTopicCommunications"],
              },
            );
          } catch (error: unknown) {
            const errorMessage = isUnauthorisedError(error)
              ? "Failed to retrieve conversation topics: Unauthorised access. Please check API credentials or permissions"
              : `Failed to retrieve conversation topics: ${error instanceof Error ? error.message : JSON.stringify(error)}`;
    
            return errorResult(errorMessage);
          }
    
          const topicIds = new Set<string>();
    
          for (const result of jobDetails.results ?? []) {
            if (result.group?.topicId) {
              topicIds.add(result.group.topicId);
            }
          }
    
          if (topicIds.size === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: `Conversation ID: ${conversationId}\nNo detected topics for this conversation.`,
                },
              ],
            };
          }
    
          const topics: Models.ListedTopic[] = [];
    
          try {
            for (const topicIdChunk of chunks(
              Array.from(topicIds.values()),
              MAX_IDS_ALLOWED_BY_API,
            )) {
              const topicsListings =
                await speechTextAnalyticsApi.getSpeechandtextanalyticsTopics({
                  ids: topicIdChunk,
                  pageSize: MAX_IDS_ALLOWED_BY_API,
                });
    
              topics.push(...(topicsListings.entities ?? []));
            }
          } catch (error: unknown) {
            const errorMessage = isUnauthorisedError(error)
              ? "Failed to retrieve conversation topics: Unauthorised access. Please check API credentials or permissions"
              : `Failed to retrieve conversation topics: ${error instanceof Error ? error.message : JSON.stringify(error)}`;
    
            return errorResult(errorMessage);
          }
    
          const topicNames = topics
            .filter((topic) => topic.name && topic.description)
            .map(({ name, description }) => ({
              name: name ?? "",
              description: description ?? "",
            }));
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify({
                  conversationId: conversationId,
                  detectedTopics: topicNames,
                }),
              },
            ],
          };
        },
      });
  • Zod schema for input validation: requires a single 'conversationId' parameter as a UUID string.
    const paramsSchema = z.object({
      conversationId: z
        .string()
        .uuid()
        .describe(
          "A UUID for a conversation. (e.g., 00000000-0000-0000-0000-000000000000)",
        ),
    });
  • src/index.ts:107-119 (registration)
    Registration of the conversation_topics tool on the MCP server. Creates the tool with dependencies (speechTextAnalyticsApi, analyticsApi), registers it by name, and wraps the call with OAuth authentication.
    const conversationTopicsTool = conversationTopics({
      speechTextAnalyticsApi,
      analyticsApi,
    });
    server.registerTool(
      conversationTopicsTool.schema.name,
      {
        description: conversationTopicsTool.schema.description,
        inputSchema: conversationTopicsTool.schema.paramsSchema.shape,
        annotations: conversationTopicsTool.schema.annotations,
      },
      withAuth(conversationTopicsTool.call),
    );
  • Generator function that splits an array into chunks of a specified size, used to batch topic ID requests respecting the API limit of 50 IDs per call.
    export function* chunks<T>(arr: T[], n: number): Generator<T[], void> {
      if (!Number.isInteger(n) || n <= 0) {
        throw new Error("Chunk size must be a positive integer");
      }
    
      for (let i = 0; i < arr.length; i += n) {
        yield arr.slice(i, i + n);
      }
    }
Behavior4/5

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

The description states 'Retrieves', indicating a read-only operation. No annotations for destructive or read-only hints exist, so the description carries the burden. It does not mention authorization or rate limits, but for a simple retrieval, the behavior is fairly transparent.

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?

Two concise sentences. First sentence states action and target, second elaborates on topic meaning. No redundant information. Efficient.

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 one required parameter, no output schema, and simple retrieval, the description is complete. It explains what topics are (business-level intents) and how they are derived. No gaps.

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 coverage is 100%, with parameter 'conversationId' well-documented in schema. The description mentions 'a specific conversation' but adds no new semantic meaning beyond the schema. Baseline 3 is appropriate.

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 it retrieves topics for a specific conversation, using specific action 'Retrieves' and resource 'Speech and Text Analytics topics'. It provides examples (cancellation, billing enquiry) and implies difference from siblings like conversation_sentiment and conversation_transcript by focusing on business-level intents.

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?

The description implicitly tells when to use it (when topics needed) but lacks explicit guidance on when not to use it or alternatives. However, the context of sibling tools makes the purpose sufficiently clear.

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/MakingChatbots/genesys-cloud-mcp-server'

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