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;
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It confirms it lists all brands and returns basic info, but it does not elaborate on what 'basic info' includes, potential pagination, or any other behavioral characteristics. This is adequate for a simple list tool but lacks depth.

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 concise sentence that is front-loaded with the action and resource. It contains no fluff or redundant information.

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?

The tool is simple with no output schema, but the description is vague about what 'basic info' entails. Since there are sibling tools that provide more detail (e.g., maasy_get_brand_context), the description could have pointed to them, but it doesn't. Adequate for a basic list but leaves some ambiguity.

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 tool has zero parameters, and the description's phrase 'all brands' implies no filtering is needed. With no parameters, the baseline is 4, and the description aligns well without needing to explain any parameter details.

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 the tool lists all brands (projects) in the maasy account with basic info. The verb 'List' and resource 'brands' are specific, and it distinguishes from siblings like maasy_get_brand_context (which targets a specific brand) and maasy_list_skills (which lists a different entity).

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

Usage Guidelines4/5

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

The context for use is clear: when you need an overview of all brands with basic info. However, it does not mention alternatives or explicitly state when not to use this tool, though sibling contrast is implied by the tool name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.