Skip to main content
Glama

list_projects

Retrieve all AICre8 projects with their IDs, names, and preview URLs for project management and deployment.

Instructions

List all your AICre8 projects with their IDs, names, and preview URLs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `listProjects()` method in AICre8Client class that makes a GET request to `/projects` endpoint and returns an object containing an array of projects with their IDs, names, URLs, and metadata.
    async listProjects(): Promise<{
      projects: Array<{
        id: string;
        url_id: string;
        name: string;
        created_at: string;
        preview_url: string | null;
        has_sandbox: boolean;
      }>;
    }> {
      return this.request('GET', '/projects');
    }
  • src/index.ts:31-52 (registration)
    Registration of the `list_projects` MCP tool using `server.tool()`. Defines the tool name, description, empty input schema ({}), and async handler that calls `client.listProjects()` and returns the result as JSON text content.
    // ── Tool: list_projects ──
    
    server.tool(
      'list_projects',
      'List all your AICre8 projects with their IDs, names, and preview URLs',
      {},
      async () => {
        try {
          const result = await client.listProjects();
          return {
            content: [
              {
                type: 'text' as const,
                text: JSON.stringify(result.projects, null, 2),
              },
            ],
          };
        } catch (err: any) {
          return { content: [{ type: 'text' as const, text: `Error: ${err.message}` }], isError: true };
        }
      },
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden. It indicates a read operation ('List') and specifies the returned fields, but lacks details on behavioral traits such as pagination, rate limits, authentication needs, or error handling. It doesn't contradict annotations, but offers minimal behavioral context beyond the basic action.

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 front-loads the core action ('List all your AICre8 projects') and adds value by specifying the returned data. There is zero waste, and every part of the sentence contributes to understanding the tool's function.

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

Completeness3/5

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

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is adequate but has gaps. It explains what the tool does and what it returns, but without annotations or output schema, it misses details like response format, error cases, or usage constraints, making it minimally viable but not fully complete.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter information, focusing instead on the tool's purpose and output details, which is sufficient given the lack of parameters.

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 ('List all your AICre8 projects') and specifies what information is returned ('with their IDs, names, and preview URLs'), which provides a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'create_project' or 'deploy_project' in terms of when to choose listing versus creation/deployment.

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

Usage Guidelines3/5

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

The description implies usage by specifying 'List all your AICre8 projects,' suggesting it's for retrieving existing projects, but it doesn't provide explicit guidance on when to use this tool versus alternatives like 'create_project' or 'deploy_project.' No exclusions or clear context for alternatives are mentioned.

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/AICre8dev/mcp-server'

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