Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

marketplace_migrate_connection

Migrate an existing external authentication connection by supplying OAuth2 tokens or basic credentials, app IDs, and account identifier to set up auth for a GHL location.

Instructions

Migrate external authentication connection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesType of authentication - basic or oauth2
appIdYesApp ID
apiKeyNoAPI Key (supported when type is basic)
scopesNoOAuth2 scopes (optional for oauth2)
expiryAtNoTimestamp for access token expiry (optional for oauth2)
expiryInNoAccess token expiry time in milliseconds (optional for oauth2)
accountIdYesConnection identifier
isDefaultNoWhether this is the default connection for the location (optional, defaults to false)
locationIdNoLocation ID Defaults to GHL_LOCATION_ID when omitted.
accessTokenNoAccess token (required when type is oauth2)
displayNameNoDisplay name for the connection (optional, defaults to accountId)
appVersionIdYesApp Version ID
refreshTokenNoRefresh token (required when type is oauth2)
basicCredentialsNoBasic auth credentials as key/value pairs (supported when type is basic). Keys are validated against the app version externalAuthConfig.fields.
Behavior1/5

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

No behavioral traits are disclosed. The description is a single terse phrase that does not indicate what side effects occur, whether it overwrites existing data, requires specific permissions, or returns anything. With no annotations providing hints (readOnlyHint=false, openWorldHint=true), the description carries the full burden, and it fails to provide any transparency about what the tool actually does beyond the name.

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

Conciseness2/5

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

The description is extremely concise (one short sentence) but not appropriately structured or informative. It lacks any front-loading of critical information beyond the name. While brevity can be good, here it sacrifices all explanatory value, making the tool cryptic. The sentence is not misleading, but it is under-specified to the point of being nearly useless guide.

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

Completeness1/5

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

For a tool with 14 parameters, no output schema, and significant complexity (nested objects, conditional fields), this description is woefully incomplete. It does not explain the migration context, prerequisites, what happens to existing connections, or any side effects. An agent cannot safely invoke this tool without additional documentation. The description must compensate for the schema's lack of high-level guidance, and it does not.

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 with each parameter described, so the baseline is 3. However, the description adds no additional meaning or context about how parameters relate to the migration process. It does not clarify how 'type', 'appId', or 'accountId' interact or what 'migrate' entails for these fields. The description is essentially redundant with the schema, providing no extra semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('Migrate') and resource ('external authentication connection'), but the exact nature of the migration is ambiguous—it could mean moving, updating, or transferring. It doesn't differentiate from sibling tools (none other use 'migrate'), but the purpose is generic enough that an agent might not know what action to take without more context.

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?

There is no guidance on when to use this tool versus alternatives. The sibling list contains no other migration tool, but the description does not explain scenarios (e.g., transferring a connection between apps, updating credentials). An agent would have to infer usage from the schema alone, which is insufficient for a complex operation.

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/AIWerk/mcp-server-ghl'

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