Skip to main content
Glama

list_integrations

List company integrations by type, including ecommerce, email, marketing, tax, shipping, accounting, and chat. Filter results to find relevant integrations quickly.

Instructions

List company integrations. GET /integrations. Optional: type (ecommerce, email, marketing, tax, shipping, accounting, chat).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by integration type: ecommerce, email, marketing, tax, shipping, accounting, chat

Implementation Reference

  • The handler function that executes the list_integrations tool logic. It parses args with Zod schema, then calls integrationService.listIntegrations() with the optional type filter.
    async function handler(client: Client, args: Record<string, unknown> | undefined) {
      const parsed = schema.safeParse(args);
      if (!parsed.success) {
        return errorResult(parsed.error.errors.map((e) => e.message).join("; "));
      }
      return handleToolCall(() => integrationService.listIntegrations(client, parsed.data));
    }
    
    export const listIntegrationsTool: Tool = {
      definition,
      handler,
    };
  • Zod validation schema defining the optional 'type' parameter (enum of integration types: ecommerce, email, marketing, tax, shipping, accounting, chat).
    const schema = z.object({
      type: z.enum(INTEGRATION_TYPES).optional(),
    });
  • Tool definition with name 'list_integrations', description, and input JSON Schema (type filter parameter, not required).
    const definition = {
      name: "list_integrations",
      description:
        "List company integrations. GET /integrations. Optional: type (ecommerce, email, marketing, tax, shipping, accounting, chat).",
      inputSchema: {
        type: "object" as const,
        properties: {
          type: {
            type: "string",
            description:
              "Filter by integration type: ecommerce, email, marketing, tax, shipping, accounting, chat",
          },
        },
        required: [],
      },
    };
  • Registration of listIntegrationsTool in the registerIntegrationTools() function which returns all integration tools as an array.
    export function registerIntegrationTools(): Tool[] {
      return [
        listIntegrationsTool,
        getIntegrationConfigTool,
        getIntegrationByKeyTool,
        listIntegrationsByKeyTool,
        listExternalInvoicesTool,
        listExternalProductsTool,
        getExternalProductTool,
        listOrderStatusesTool,
      ];
    }
  • The service layer function that makes the actual GET /integrations API call with optional query parameters (type, include, itemPerPage, pageNo).
    export async function listIntegrations(
      client: Client,
      params?: ListIntegrationsParams
    ): Promise<unknown> {
      const search = new URLSearchParams();
      if (params?.type) search.append("type", params.type);
      if (params?.include) search.append("include", params.include);
      if (params?.itemPerPage != null) search.append("itemPerPage", String(params.itemPerPage));
      if (params?.pageNo != null) search.append("pageNo", String(params.pageNo));
      const q = search.toString();
      return client.get<unknown>(`/integrations${q ? `?${q}` : ""}`);
    }
Behavior2/5

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

No annotations provided. Description is minimal, lacking details on read-only nature, pagination, rate limits, or other behavioral traits.

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?

Extremely concise: one sentence with URL and optional filter options. No filler.

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?

Adequate for a simple list tool with one optional parameter, but lacks info on response format or pagination. Could benefit from more context.

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?

Schema already describes the single parameter with 100% coverage. Description adds no new meaning beyond repeating the options.

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) and resource (company integrations), with optional filter. It doesn't differentiate from sibling list tools, but the resource name distinguishes it.

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?

Mentions optional type filter with examples, but no guidance on when to use this tool versus alternatives like list_integrations_by_key.

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

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