Skip to main content
Glama

list_businesses

List all businesses accessible by the current user, with paginated results.

Instructions

List all businesses accessible by the current user. Returns paginated results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated fields to return
limitNoNumber of results (default 25)
afterNoPagination cursor for next page

Implementation Reference

  • The handler function (registered as server.tool('list_businesses', ...)) that calls client.get('/me/businesses', params) to list all businesses accessible by the current user.
    // ─── list_businesses ──────────────────────────────────────────
    server.tool(
      "list_businesses",
      "List all businesses accessible by the current user. Returns paginated results.",
      {
        fields: z.string().optional().describe("Comma-separated fields to return"),
        limit: z.number().optional().default(25).describe("Number of results (default 25)"),
        after: z.string().optional().describe("Pagination cursor for next page"),
      },
      async ({ fields, limit, after }) => {
        try {
          const params: Record<string, unknown> = {};
          if (fields) params.fields = fields;
          if (limit) params.limit = limit;
          if (after) params.after = after;
          const { data, rateLimit } = await client.get(`/me/businesses`, params);
          return { content: [{ type: "text" as const, text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
  • Input schema for list_businesses: optional 'fields' (string), 'limit' (number, default 25), and 'after' (string for pagination).
    {
      fields: z.string().optional().describe("Comma-separated fields to return"),
      limit: z.number().optional().default(25).describe("Number of results (default 25)"),
      after: z.string().optional().describe("Pagination cursor for next page"),
    },
  • The registerBusinessTools function wraps all business tool registrations including list_businesses.
    export function registerBusinessTools(server: McpServer, client: AdsClient): void {
  • src/index.ts:88-90 (registration)
    Registration call: registerBusinessTools(server, client) invoked in the main server initialization.
    // --- Account & Business ---
    registerAccountTools(server, client);
    registerBusinessTools(server, client);
  • The AdsClient.get() method used by the handler to make the HTTP GET request to the Meta API.
    async get(
      path: string,
      params?: Record<string, unknown>
    ): Promise<ClientResponse> {
      return this.request("GET", path, params);
    }
Behavior2/5

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

With no annotations, the description mentions 'Returns paginated results', which is a useful behavioral trait. However, it does not disclose read-only nature, authentication needs, rate limits, or side effects. Minimal additional transparency beyond what is standard.

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 extremely concise with two clear sentences. No redundant or unnecessary information; every word serves a purpose.

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?

The description lacks details about the return structure (e.g., fields of a business object). Given no output schema, the agent cannot understand the response format. For a listing tool, this is a significant gap.

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 input schema has 100% coverage for all three parameters (fields, limit, after). The description adds no extra meaning beyond the schema, simply stating pagination. 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 'List all businesses accessible by the current user', specifying the verb and resource. It distinguishes itself from siblings like 'get_business' (singular) and 'list_business_ad_accounts' (filtered), though it could be slightly more explicit about the scope (all businesses across accounts).

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?

No guidance on when to use this tool versus alternatives such as 'get_business' for a single business or other list tools. No exclusions or context for selection are provided.

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/mikusnuz/meta-ads-mcp'

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