Skip to main content
Glama

delete_credential

Remove a specific credential for a consumer in the APISIX-MCP server by providing the username and credential ID to manage access securely.

Instructions

Delete a credential for a consumer

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYescredential id
usernameYesconsumer username

Implementation Reference

  • Inline handler implementation for the 'delete_credential' tool. It makes a DELETE request to the admin API to remove the specified credential for a consumer.
    server.tool("delete_credential", "Delete a credential for a consumer", DeleteCredentialSchema.shape, async (args) => {
      return await makeAdminAPIRequest(`/consumers/${args.username}/credentials/${args.id}`, "DELETE");
    });
  • Zod input schema for the 'delete_credential' tool, requiring 'username' and 'id'.
    export const DeleteCredentialSchema = z.object({
      username: ConsumerSchema.shape.username,
      id: z.string().describe("credential id"),
    });
  • Registration of the 'delete_credential' tool on the MCP server using server.tool().
    server.tool("delete_credential", "Delete a credential for a consumer", DeleteCredentialSchema.shape, async (args) => {
      return await makeAdminAPIRequest(`/consumers/${args.username}/credentials/${args.id}`, "DELETE");
    });
  • Supporting utility function that performs HTTP requests to the APISIX admin API, used by the delete_credential handler.
    export async function makeAdminAPIRequest(
      path: string,
      method: string = "GET",
      data?: object
    ): Promise<CallToolResult> {
      const baseUrl = `${APISIX_SERVER_HOST}:${APISIX_ADMIN_API_PORT}${APISIX_ADMIN_API_PREFIX}`;
      const url = `${baseUrl}${path}`;
    
      try {
        const response = await axios({
          method,
          url,
          data,
          headers: {
            "X-API-KEY": APISIX_ADMIN_KEY,
            "Content-Type": "application/json",
          },
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          console.error(`Request failed: ${method} ${url}`);
          console.error(
            `Status: ${error.response?.status}, Error: ${error.message}`
          );
    
          if (error.response?.data) {
            try {
              const stringifiedData = JSON.stringify(error.response.data);
              console.error(`Response data: ${stringifiedData}`);
            } catch {
              console.error(`Response data: [Cannot parse as JSON]`);
            }
          }
    
          return {
            isError: true,
            content: [
              {
                type: "text",
                text: JSON.stringify(
                  `Status: ${error.response?.status}\nMessage: ${error.message}
    Data:\n${JSON.stringify(error.response?.data || {}, null, 2)}`,
                  null,
                  2
                ),
              },
            ],
          };
        } else {
          return {
            isError: true,
            content: [
              {
                type: "text",
                text: JSON.stringify(error, null, 2),
              },
            ],
          };
        }
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Delete', implying a destructive mutation, but fails to mention critical details such as permissions required, whether the deletion is permanent or reversible, or any side effects (e.g., impact on associated consumers). This is a significant gap for a destructive tool.

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, direct sentence with no wasted words, efficiently conveying the core action and target. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 destructive tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permanence, auth needs), expected outcomes, or error handling, which are crucial for safe and correct usage in this 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%, with clear parameter descriptions ('credential id' and 'consumer username'), so the schema provides adequate documentation. The description does not add any extra meaning beyond this, such as format examples or relationships between parameters, which is acceptable given the 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 action ('Delete') and the resource ('a credential for a consumer'), making the purpose unambiguous. However, it does not distinguish this tool from sibling tools like 'delete_resource' or 'delete_secret', which might also handle deletion operations in this system, so it misses full sibling differentiation.

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 does not mention prerequisites (e.g., needing an existing credential), exclusions, or refer to sibling tools like 'delete_resource' that might handle similar deletions, leaving the agent without context for selection.

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/api7/apisix-mcp'

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