Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_payment_integration_provider_list

Read-onlyIdempotent

Retrieve a paginated list of whitelabel integration providers, filtered by name, to manage payment integrations and explore provider information.

Instructions

List White-label Integration Providers The "List White-label Integration Providers" API allows to retrieve a paginated list of integration providers. Customize your results by filtering whitelabel integration providers(which are built directly on top of Authorize.net or NMI) based on name or paginate through the list using the provided query parameters. This endpoint provides a straightforward way to explore and retrieve integration provider information. Endpoint: GET /payments/integrations/provider/whitelabel (Version header: v3; source: v3/payments-v3.json) Requires a Sub-Account (location) token. OAuth scopes: payments/integration.readonly Pagination params: limit, offset — pass them to page through full result sets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_payment_integration_provider_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYeslocation Id / company Id based on altType
limitNoThe maximum number of items to be included in a single page of results
offsetNoThe starting index of the page, indicating the position from which the results should be retrieved.
altTypeYesAlt Type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds meaningful context beyond that: sub-account (location) token requirement, OAuth scope payments/integration.readonly, endpoint, version header, and pagination behavior. It stops short of describing the response shape, but adds substantial auth/scope context.

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

Conciseness3/5

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

The core list scope and pagination guidance are front-loaded, but the second sentence ('endpoint provides a straightforward way to explore and retrieve integration provider information') is filler that repeats the purpose already stated. Some trimming would improve it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only paginated list with no output schema, the description covers auth requirements, OAuth scope, endpoint, and pagination adequately. The only gap is the unsupported 'filter by name' claim, which an agent might wrongly assume is possible.

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 description coverage is 100%, so baseline is 3; the description reinforces pagination via limit/offset which matches the schema. However, its claim of filtering 'based on name' does not correspond to any actual parameter, adding slight confusion rather than enrichment.

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 opens with a specific verb (List) and resource (White-label Integration Providers) and clarifies the resource type as providers built on Authorize.net or NMI, distinguishing it from the create/payment custom-provider siblings. An agent can identify the operation without opening the schema.

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?

It states the tool is for exploring/retrieving integration provider info and mentions pagination, which implies usage, but gives no explicit when-to-use vs. alternatives (e.g., vs. ghl_payment_custom_provider_* tools). The mention of filtering 'based on name' is misleading since no name parameter exists in the schema.

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

Deploy Server

Other Tools