Skip to main content
Glama

maasy_list_brands

List all brands or projects in your Maasy account with basic details to view and manage your marketing initiatives.

Instructions

List all brands (projects) in your maasy account with basic info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:62-67 (registration)
    Registration of the 'maasy_list_brands' MCP tool. It has no input parameters (empty schema '{}') and delegates to toolHandler('list_brands'), which calls the gateway with the 'list_brands' tool name.
    server.tool(
      "maasy_list_brands",
      "List all brands (projects) in your maasy account with basic info",
      {},
      toolHandler("list_brands")
    );
  • Generic 'toolHandler' wrapper function that executes the actual tool logic. For 'maasy_list_brands', it calls callGateway('list_brands', args) which makes an HTTP POST to the MCP gateway edge function. The result is returned as JSON text content.
    function toolHandler(toolName: string, argsFn?: (args: Record<string, unknown>) => Record<string, unknown>) {
      return async (args: Record<string, unknown>) => {
        try {
          const gatewayArgs = argsFn ? argsFn(args) : args;
          // Auto-inject default project_id if not provided
          if (DEFAULT_PROJECT_ID && !gatewayArgs.project_id) {
            gatewayArgs.project_id = DEFAULT_PROJECT_ID;
          }
          const result = await callGateway(toolName, gatewayArgs);
          return { content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }] };
        } catch (e: unknown) {
          return {
            content: [{ type: "text" as const, text: `Error: ${e instanceof Error ? e.message : String(e)}` }],
            isError: true,
          };
        }
      };
    }
  • The 'callGateway' function in supabase.ts sends the tool name and args to the MCP gateway edge function via HTTP POST. For 'maasy_list_brands', it sends { tool: 'list_brands', args: {} } to the Supabase edge function endpoint.
    export async function callGateway(tool: string, args: Record<string, unknown> = {}): Promise<unknown> {
      const res = await fetch(gatewayUrl, {
        method: "POST",
        headers: {
          "Content-Type": "application/json",
          [authHeader.name]: authHeader.value,
        },
        body: JSON.stringify({ tool, args }),
      });
    
      const data = await res.json();
    
      if (!res.ok) {
        throw new Error(data.error || `Gateway error (${res.status})`);
      }
    
      return data.result;
    }
Behavior4/5

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

No annotations are present, so the description must convey behavioral traits. It indicates a read-only listing operation with no side effects. However, it doesn't specify authentication needs or rate limits, though for a simple list tool this is sufficient.

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?

A single, clear sentence with no wasted words. The verb 'List' is front-loaded, making the purpose immediately obvious.

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

Completeness4/5

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

Given the tool's simplicity (no parameters, no output schema), the description is mostly complete. It tells the agent what it does and what to expect ('basic info'). Slightly improved by specifying common fields, but adequate.

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 no parameters and 100% coverage. The description adds value by hinting at the output with 'basic info', which implies limited fields like name and ID, though not detailed.

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

Purpose5/5

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

The description clearly states it lists all brands (projects) with basic info. It uses a specific verb 'list' and resource 'brands', and differentiates from sibling 'maasy_get_brand_context' which likely provides detailed info for a single brand.

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?

No explicit when-to-use or alternatives are provided. The usage is implied: when a user wants an overview of all brands, but no guidance on when not to use it or comparison with other tools like maasy_get_brand_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/Jbelieve/mcp-server'

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