Skip to main content
Glama
confluentinc

mcp-confluent

Official
by confluentinc

create-topic-tags

Define and organize new topic tags in Confluent Cloud using the Schema Registry REST API to streamline data categorization and management.

Instructions

Create new tag definitions in Confluent Cloud.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseUrlNoThe base URL of the Schema Registry REST API.
tagsYesArray of tag definitions to create

Implementation Reference

  • The handle() method in CreateTopicTagsHandler that implements the core logic: parses args, sets endpoint if provided, creates tag definitions for kafka_topic entities, POSTs to /catalog/v1/types/tagdefs, and returns success/error response.
    async handle(
      clientManager: ClientManager,
      toolArguments: Record<string, unknown>,
    ): Promise<CallToolResult> {
      const { tags, baseUrl } = createTagsArguments.parse(toolArguments);
    
      if (baseUrl !== undefined && baseUrl !== "") {
        clientManager.setConfluentCloudSchemaRegistryEndpoint(baseUrl);
      }
    
      const pathBasedClient = wrapAsPathBasedClient(
        clientManager.getConfluentCloudSchemaRegistryRestClient(),
      );
    
      const tagDefinitions = tags.map((tag) => ({
        entityTypes: ["kafka_topic"],
        name: tag.tagName,
        description: tag.description,
      }));
    
      const { data: response, error } = await pathBasedClient[
        "/catalog/v1/types/tagdefs"
      ].POST({
        body: tagDefinitions,
      });
    
      if (error) {
        return this.createResponse(
          `Failed to create tag: ${JSON.stringify(error)}`,
          true,
        );
      }
      return this.createResponse(
        `Successfully created tag: ${JSON.stringify(response)}`,
      );
    }
  • Zod schema defining input parameters: optional baseUrl (Schema Registry endpoint) and non-empty array of tags with tagName and optional description.
    const createTagsArguments = z.object({
      baseUrl: z
        .string()
        .describe("The base URL of the Schema Registry REST API.")
        .url()
        .default(() => env.SCHEMA_REGISTRY_ENDPOINT ?? "")
        .optional(),
      tags: z
        .array(
          z.object({
            tagName: z.string().describe("Name of the tag to create").nonempty(),
            description: z
              .string()
              .describe("Description for the tag")
              .default("Tag created via API"),
          }),
        )
        .nonempty()
        .describe("Array of tag definitions to create"),
    });
  • Registration of the CreateTopicTagsHandler instance in the ToolFactory's static handlers Map, keyed by ToolName.CREATE_TOPIC_TAGS.
    [ToolName.CREATE_TOPIC_TAGS, new CreateTopicTagsHandler()],
  • Enum constant defining the tool name string "create-topic-tags" used across the codebase for consistency.
    CREATE_TOPIC_TAGS = "create-topic-tags",
  • Tool configuration including name, description, and inputSchema, returned by the handler for tool registration.
    getToolConfig(): ToolConfig {
      return {
        name: ToolName.CREATE_TOPIC_TAGS,
        description: "Create new tag definitions in Confluent Cloud.",
        inputSchema: createTagsArguments.shape,
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a creation operation but doesn't mention authentication requirements, rate limits, whether tags are globally unique, what happens on duplicate tag names, or the response format. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with every word earning its place in conveying the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address behavioral aspects like permissions, error conditions, or response format, nor does it provide usage context relative to sibling tools. The 100% schema coverage helps but doesn't compensate for the missing operational context.

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 schema fully documents both parameters (baseUrl and tags array). The description adds no additional parameter semantics beyond what's in the schema, such as explaining tag naming conventions or baseUrl construction. The baseline score of 3 reflects adequate but minimal value addition.

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 action ('Create new tag definitions') and resource ('in Confluent Cloud'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'add-tags-to-topic' or 'delete-tag', which would require mentioning this creates tag definitions rather than applying or removing them.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing existing topics or clusters), contrast with 'add-tags-to-topic' (which applies tags to entities) or 'delete-tag', or specify appropriate contexts for tag creation versus other operations.

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

Related 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/confluentinc/mcp-confluent'

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