Skip to main content
Glama

get_integration_by_key

Retrieve global integration information by specifying the integration key name. Use to get details for any supported integration like Avalara, BigCommerce, or Shopify.

Instructions

Get global integration info by key name. GET /integrations/{keyName}/get. 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 executes the tool logic. It validates input via Zod schema, then calls integrationService.getIntegrationByKey(client, keyName).
    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.getIntegrationByKey(client, parsed.data.keyName)
      );
    }
  • Zod schema for input validation: keyName must be one of the valid integration key names (enum).
    const schema = z.object({
      keyName: z.enum(INTEGRATION_KEY_NAMES, {
        errorMap: () => ({ message: "keyName must be a valid integration key (e.g. xero, shopify, avalara)" }),
      }),
    });
  • The tool export as a Tool object combining definition and handler. The definition has name 'get_integration_by_key'.
    export const getIntegrationByKeyTool: Tool = {
      definition,
      handler,
    };
  • Registration of getIntegrationByKeyTool in the array of all integration tools returned by registerIntegrationTools().
    export function registerIntegrationTools(): Tool[] {
      return [
        listIntegrationsTool,
        getIntegrationConfigTool,
        getIntegrationByKeyTool,
        listIntegrationsByKeyTool,
        listExternalInvoicesTool,
        listExternalProductsTool,
        getExternalProductTool,
        listOrderStatusesTool,
      ];
    }
  • The underlying API service function that makes the GET /integrations/{keyName}/get HTTP call via the client.
    export async function getIntegrationByKey(
      client: Client,
      keyName: string
    ): Promise<unknown> {
      return client.get<unknown>(`/integrations/${encodeURIComponent(keyName)}/get`);
    }
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like read-only nature, authentication needs, or rate limits. It only mentions it's a GET request (via the endpoint), but does not explicitly confirm it's safe/non-destructive. No indication of what happens if key is invalid or performance considerations.

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?

Very concise: two sentences plus endpoint and key list. However, the endpoint string (GET /integrations/{keyName}/get) is slightly redundant since the name implies HTTP. Still, no wasted words, and the list is necessary. Front-loads the purpose.

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?

For a simple one-param getter with no output schema, the description covers the main purpose and parameter. But it lacks description of the return value (what is 'global integration info'?) and does not distinguish this from sibling tools like list_integrations_by_key or get_integration_config. Adequate but could be more complete.

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%, and the schema's property description already lists all valid key values. The tool's description repeats some examples but adds no new meaning beyond schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 retrieves global integration info by key name, includes the endpoint, and lists valid key values. It effectively distinguishes this tool from siblings like list_integrations (which lists all) and get_integration_config (which likely gets config). The verb 'get' and resource 'global integration info' are specific.

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?

The description implies usage (use this to get integration info by key) but does not explicitly state when to use it versus alternatives like list_integrations or list_integrations_by_key. No when-not-to-use guidance or prerequisites are provided. The list of valid keys is helpful but insufficient for decision-making.

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