Skip to main content
Glama
fikri2992

MCP API Server

by fikri2992

api_delete

Remove resources from external APIs by sending HTTP DELETE requests through the MCP API Server. Specify the target URL and optional headers to delete data programmatically.

Instructions

Make an HTTP DELETE request to the specified URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to make the DELETE request to
headersNoOptional headers to include in the request

Implementation Reference

  • Defines the MCPTool specification for 'api_delete' including name, description, and input schema for URL and optional headers.
    export const API_DELETE_TOOL: MCPTool = {
      name: 'api_delete',
      description: 'Make an HTTP DELETE request to the specified URL',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            format: 'uri',
            description: 'The URL to make the DELETE request to',
          },
          headers: {
            type: 'object',
            description: 'Optional headers to include in the request',
            additionalProperties: {
              type: 'string',
            },
          },
        },
        required: ['url'],
      },
    };
  • src/tools.ts:138-142 (registration)
    Registers 'api_delete' in the TOOL_MAP lookup used by mcp-server to validate tool existence.
    export const TOOL_MAP: Record<string, MCPTool> = {
      [API_GET_TOOL.name]: API_GET_TOOL,
      [API_POST_TOOL.name]: API_POST_TOOL,
      [API_PUT_TOOL.name]: API_PUT_TOOL,
      [API_DELETE_TOOL.name]: API_DELETE_TOOL,
  • Registers the MCP list_tools handler which exposes api_delete (via ALL_API_TOOLS) to clients.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      this.log('Received list_tools request');
      return {
        tools: ALL_API_TOOLS,
      };
    });
  • The dispatch handler in handleToolCall that executes api_delete by calling apiClient.delete.
    case 'api_delete':
      return await this.apiClient.delete(validatedRequest.url, validatedRequest.headers);
  • Core implementation of the DELETE request using axios makeRequest method.
    async delete(url: string, headers?: Record<string, string>): Promise<APIResponse | ErrorResponse> {
      return this.makeRequest({
        url,
        method: 'DELETE',
        headers,
      });
    }
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 basic action without disclosing behavioral traits such as authentication needs, rate limits, error handling, or what 'DELETE' implies (e.g., resource removal). It's minimal and lacks critical operational details.

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, clear sentence with zero waste, front-loaded with the core action. It's appropriately sized for the tool's purpose without unnecessary elaboration.

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?

Given no annotations, no output schema, and a tool that performs a potentially destructive HTTP DELETE operation, the description is incomplete. It fails to address key aspects like response format, error cases, or safety considerations, leaving significant gaps for an agent.

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 already documents the 'url' and 'headers' parameters fully. The description adds no additional meaning beyond what the schema provides, such as examples or constraints, meeting the baseline for high 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 ('Make an HTTP DELETE request') and target ('to the specified URL'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like api_get or api_post beyond the HTTP method, missing explicit sibling distinction.

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 like api_post or api_put for similar operations, nor does it mention any prerequisites or exclusions. It lacks context for selection among HTTP method tools.

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/fikri2992/mcp0'

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