Skip to main content
Glama
fikri2992

MCP API Server

by fikri2992

api_post

Send HTTP POST requests to external APIs through the MCP API Server to transmit data or trigger actions at specified endpoints.

Instructions

Make an HTTP POST request to the specified URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to make the POST request to
bodyNoThe request body (string or JSON object)
headersNoOptional headers to include in the request

Implementation Reference

  • Defines the MCPTool schema for the 'api_post' tool, including input validation for URL, optional body, and headers.
    export const API_POST_TOOL: MCPTool = {
      name: 'api_post',
      description: 'Make an HTTP POST request to the specified URL',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            format: 'uri',
            description: 'The URL to make the POST request to',
          },
          body: {
            oneOf: [
              { type: 'string' },
              { type: 'object' },
            ],
            description: 'The request body (string or JSON object)',
          },
          headers: {
            type: 'object',
            description: 'Optional headers to include in the request',
            additionalProperties: {
              type: 'string',
            },
          },
        },
        required: ['url'],
      },
    };
  • src/tools.ts:138-143 (registration)
    Registers the 'api_post' tool in TOOL_MAP for quick lookup during tool validation and dispatching in the MCP server.
    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,
    };
  • The handler logic for the 'api_post' tool call, which invokes APIClient.post to perform the HTTP POST request.
    case 'api_post':
      return await this.apiClient.post(
        validatedRequest.url,
        validatedRequest.body,
        validatedRequest.headers
      );
  • The APIClient.post method that executes the actual HTTP POST request using axios, handling body serialization and error management.
    /**
     * Makes a POST request
     */
    async post(
      url: string,
      body?: string | object,
      headers?: Record<string, string>
    ): Promise<APIResponse | ErrorResponse> {
      return this.makeRequest({
        url,
        method: 'POST',
        body,
        headers,
  • Registers the MCP list_tools handler that exposes ALL_API_TOOLS (including 'api_post') to clients.
    // Register list tools handler
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      this.log('Received list_tools request');
      return {
        tools: ALL_API_TOOLS,
      };
    });
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 of behavioral disclosure. It mentions making a POST request but doesn't describe potential side effects (e.g., data modification, authentication needs, rate limits, error handling, or response format). For a tool that performs HTTP operations with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 function without unnecessary words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 the complexity of HTTP operations (with potential for side effects, authentication, and varied responses), no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits, error handling, and what to expect from the response, which are crucial for an AI agent to use this tool effectively.

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?

The schema description coverage is 100%, with clear descriptions for all parameters (url, body, headers). The description adds no additional meaning beyond what the schema provides, such as examples or constraints. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 POST request') and target ('to the specified URL'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its siblings (api_delete, api_get, api_put) beyond the HTTP method, which is why it doesn't reach a score of 5.

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_put or api_get, nor does it mention any prerequisites or context for when POST requests are appropriate (e.g., for creating resources). It simply states what the tool does without usage context.

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