Skip to main content
Glama

list_integrations_by_key

Retrieve a list of company integrations filtered by a specific integration key name, such as avalara, shopify, or xero.

Instructions

List company integrations by key name. GET /integrations/{keyName}/list. keyName: avalara, bigcommerce, customRate, fedex, flatRate, freeShipping, freshBooksCloudAccounting, google, mailchimp, monsoonStoneEdge, myob, pickupInStore, quickbooks, saasu, salesforce, shipBy, shipperHq, shippingZone, shopify, slack, smtp, taxamo, thomsonreuters, ups, upsShippingProtection, usps, vertex, xero.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNameYesIntegration key name (required). One of: avalara, bigcommerce, customRate, fedex, flatRate, freeShipping, freshBooksCloudAccounting, google, mailchimp, monsoonStoneEdge, myob, pickupInStore, quickbooks, saasu, salesforce, shipBy, shipperHq, shippingZone, shopify, slack, smtp, taxamo, thomsonreuters, ups, upsShippingProtection, usps, vertex, xero

Implementation Reference

  • The handler function that validates args via Zod schema and calls integrationService.listIntegrationsByKey.
    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.listIntegrationsByKey(client, parsed.data.keyName)
      );
    }
    
    export const listIntegrationsByKeyTool: Tool = {
      definition,
      handler,
    };
  • Zod schema for input validation: keyName must be one of the INTEGRATION_KEY_NAMES enum values.
    const schema = z.object({
      keyName: z.enum(INTEGRATION_KEY_NAMES, {
        errorMap: () => ({ message: "keyName must be a valid integration key" }),
      }),
    });
  • registerIntegrationTools() includes listIntegrationsByKeyTool in the array returned to the central tool registry.
    export function registerIntegrationTools(): Tool[] {
      return [
        listIntegrationsTool,
        getIntegrationConfigTool,
        getIntegrationByKeyTool,
        listIntegrationsByKeyTool,
        listExternalInvoicesTool,
        listExternalProductsTool,
        getExternalProductTool,
        listOrderStatusesTool,
      ];
    }
  • The service function that makes the actual HTTP GET /integrations/{keyName}/list API call.
    /** GET /integrations/{keyName}/list – list company integrations by key name. */
    export async function listIntegrationsByKey(
      client: Client,
      keyName: string
    ): Promise<unknown> {
      return client.get<unknown>(`/integrations/${encodeURIComponent(keyName)}/list`);
    }
  • INTEGRATION_KEY_NAMES constant defining the valid enum values for the keyName parameter.
    export const INTEGRATION_KEY_NAMES = [
      "avalara",
      "bigcommerce",
      "customRate",
      "fedex",
      "flatRate",
      "freeShipping",
      "freshBooksCloudAccounting",
      "google",
      "mailchimp",
      "monsoonStoneEdge",
      "myob",
      "pickupInStore",
      "quickbooks",
      "saasu",
      "salesforce",
      "shipBy",
      "shipperHq",
      "shippingZone",
      "shopify",
      "slack",
      "smtp",
      "taxamo",
      "thomsonreuters",
      "ups",
      "upsShippingProtection",
      "usps",
      "vertex",
      "xero",
    ] as const;
Behavior2/5

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

No annotations exist, and the description does not disclose any behavioral traits such as read-only nature, rate limits, authentication requirements, or potential side effects. It only states the basic operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with one sentence and a list. It is front-loaded with the purpose. However, it could be structured better by separating purpose from technical details.

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?

No output schema exists, so the description should explain the return value structure. It does not describe what fields the listed integrations contain, leaving the agent uninformed about output format.

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 coverage is 100%, so baseline is 3. The description redundantly lists the allowed keyName values already present in the schema, adding no additional meaning or context beyond what the schema provides.

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 integrations filtered by key name, with a specific endpoint and list of valid keys, distinguishing it from the sibling list_integrations which likely returns all integrations.

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 description implies use for a specific key via the keyName parameter, and the context of sibling tools suggests a general list_integrations for all. However, no explicit when-not-guidance or alternative mention is 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/rhinosaas/rebillia-mcp-server'

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