Skip to main content
Glama

delete_plugin_metadata

Remove plugin metadata from the APISIX-MCP server by specifying the plugin name, ensuring streamlined backend configuration and resource management.

Instructions

Delete plugin metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesplugins name

Implementation Reference

  • Inline handler function for the 'delete_plugin_metadata' tool. It performs a DELETE request to the admin API endpoint `/plugin_metadata/${name}`.
    server.tool("delete_plugin_metadata", "Delete plugin metadata", DeletePluginMetadataSchema.shape, async (args) => {
      return await makeAdminAPIRequest(`/plugin_metadata/${args.name}`, "DELETE");
    });
  • Zod schema for input validation of the 'delete_plugin_metadata' tool, requiring a 'name' string.
    export const DeletePluginMetadataSchema = z.object({
      name: z.string().describe("plugins name"),
    });
  • Registration of the 'delete_plugin_metadata' tool on the MCP server, including description, input shape from schema, and inline handler.
    server.tool("delete_plugin_metadata", "Delete plugin metadata", DeletePluginMetadataSchema.shape, async (args) => {
      return await makeAdminAPIRequest(`/plugin_metadata/${args.name}`, "DELETE");
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action ('Delete') without disclosing behavioral traits. It lacks details on permissions needed, whether deletion is permanent or reversible, side effects, or error handling, which is critical for a destructive operation.

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

Conciseness3/5

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

The description is extremely concise ('Delete plugin metadata'), which is efficient but under-specified. It lacks necessary elaboration for a destructive tool, making it more sparse than appropriately concise, though it is front-loaded with the core action.

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 fails to explain what plugin metadata is, the impact of deletion, or what to expect upon success/failure, leaving significant gaps in understanding for safe and effective 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 100% description coverage, documenting the single parameter 'name' as 'plugins name'. The description adds no parameter information beyond this, but with zero parameters explicitly mentioned and high schema coverage, the baseline is appropriately met without redundancy.

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

Purpose2/5

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

The description 'Delete plugin metadata' is a tautology that restates the tool name with minimal elaboration. It specifies the verb ('Delete') and resource ('plugin metadata'), but provides no additional context about what plugin metadata is or what deletion entails, making it vague beyond the obvious.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, consequences, or sibling tools like 'create_or_update_plugin_metadata' or 'get_plugin_metadata', leaving the agent with no context for decision-making.

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