Skip to main content
Glama

list_apis

Retrieve available APIs from Eolink OpenAPI for a specific project and space to enable API integration and management in Windsurf IDE.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoProject ID
spaceIdNoSpace ID

Implementation Reference

  • Handler function for the list_apis tool that fetches APIs using getApis helper and returns formatted JSON response.
    async ({ projectId, spaceId }) => {
      const apis = await this.getApis(projectId, spaceId );
      return {
        content: [{ 
          type: "text", 
          text: JSON.stringify({ apis }, null, 2) 
        }]
      };
    }
  • Zod input schema defining optional projectId and spaceId parameters for the list_apis tool.
    { projectId: z.string().optional().describe("Project ID")  , spaceId: z.string().optional().describe("Space ID") },
  • Registration of the list_apis MCP tool including name, schema, and inline handler function.
    this.server.tool(
      "list_apis",
      { projectId: z.string().optional().describe("Project ID")  , spaceId: z.string().optional().describe("Space ID") },
      async ({ projectId, spaceId }) => {
        const apis = await this.getApis(projectId, spaceId );
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({ apis }, null, 2) 
          }]
        };
      }
    );
  • Caching helper method getApis that calls eolinkService.getApis and stores results in this.apis cache.
    private async getApis(projectId: string='FuP13lBce885f9b8437ad8346d3b8576eaf134272a61f7d', spaceId?: string): Promise<Api[]> {
      // Check cache first
      if (!this.apis[projectId]) {
        try {
          this.apis[projectId] = await eolinkService.getApis(projectId, spaceId);
          console.log(`Loaded ${this.apis[projectId].length} APIs for project ${projectId}`);
        } catch (error) {
          console.error(`Error loading APIs for project ${projectId}:`, error);
        }
      }
      return this.apis[projectId];
    }
  • Core helper implementation of getApis that performs HTTP GET request to Eolink's API management endpoint to list APIs.
    async getApis(projectId: string=this.projectId, spaceId: string=this.spaceId): Promise<Api[]> {
      try {
        let url = `${this.baseUrl}/v3/api-management/apis?project_id=${projectId}&page=1&size=999`;
        
        // Add space_id parameter if provided
        if (spaceId) {
          url += `&space_id=${spaceId}`;
        }
        
        const response = await axios.get(url, {
          headers: this.getHeaders(),
        });
        return  response.data.data.items || [];
      } catch (error) {
        console.error(`Error fetching APIs for project ${projectId}:`, error);
        return [];
      }
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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?

Tool has no description.

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/scarqin/mcp-apikit'

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