Skip to main content
Glama

List Tags

list_tags

Retrieve project-level tags from the sanctioned taxonomy to organize and categorize content in Codecks project management workflows.

Instructions

List project-level tags (sanctioned taxonomy).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration and handler for the 'list_tags' MCP tool. Registers the tool with title 'List Tags', description 'List project-level tags (sanctioned taxonomy).', and an empty input schema. The handler calls client.listTags() and returns the result wrapped in finalizeToolResult().
    server.registerTool(
      "list_tags",
      {
        title: "List Tags",
        description: "List project-level tags (sanctioned taxonomy).",
        inputSchema: z.object({}),
      },
      async () => {
        try {
          const result = await client.listTags();
          return {
            content: [{ type: "text", text: JSON.stringify(finalizeToolResult(result)) }],
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(finalizeToolResult(handleError(err))),
              },
            ],
          };
        }
      },
    );
  • Client implementation of listTags() method. Performs a GraphQL query to fetch masterTags with fields id, name, and color from the Codecks API. Uses the extractList helper to parse the response and returns the tags in a { tags: [...] } format.
    async listTags(): Promise<Record<string, unknown>> {
      const result = await query({
        _root: [{ account: [{ masterTags: ["id", "name", "color"] }] }],
      });
      return { tags: this.extractList(result, "masterTags") };
    }
  • Helper method extractList() used by listTags to extract arrays from nested GraphQL response structures. Navigates through the result object to find and return the array at the specified key (e.g., 'masterTags').
    private extractList(result: Record<string, unknown>, key: string): Record<string, unknown>[] {
      for (const val of Object.values(result)) {
        if (typeof val === "object" && val !== null) {
          const obj = val as Record<string, unknown>;
          if (Array.isArray(obj[key])) return obj[key] as Record<string, unknown>[];
          for (const inner of Object.values(obj)) {
            if (typeof inner === "object" && inner !== null) {
              const innerObj = inner as Record<string, unknown>;
              if (Array.isArray(innerObj[key])) return innerObj[key] as Record<string, unknown>[];
            }
          }
        }
      }
      return [];
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation ('List') but doesn't disclose behavioral traits like pagination, sorting, error handling, or rate limits. The phrase 'sanctioned taxonomy' hints at governance but lacks detail on what that entails operationally.

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 front-loads the core purpose ('List project-level tags') and adds clarifying detail without waste. Every word earns its place, making it highly concise and well-structured.

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

Completeness3/5

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

Given 0 parameters and no output schema, the description is adequate for a simple list tool but incomplete. It lacks details on return format, error cases, or the implications of 'sanctioned taxonomy'. With no annotations, more behavioral context would improve completeness for agent use.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds context about 'project-level' scope and 'sanctioned taxonomy', which provides semantic value beyond the empty schema. This compensates well for the lack of parameters.

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 ('List') and resource ('project-level tags') with the clarifying detail 'sanctioned taxonomy'. It distinguishes from siblings like 'get_tag_registry' by focusing on listing rather than retrieving registry data. However, it doesn't explicitly differentiate from other list tools (e.g., 'list_cards', 'list_projects'), which slightly limits specificity.

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 when to choose 'list_tags' over 'get_tag_registry' or other list tools, nor does it specify any prerequisites or exclusions. This leaves the agent without contextual usage cues.

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/rangogamedev/codecks-mcp'

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