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

ghl-mcp-server-v2

by zackscriven

ghl_marketplace_uninstall_application

DestructiveIdempotent

Uninstall an application from a company or location to remove its access and stop all related functionality. Provide the app ID and company or location ID to target the removal.

Instructions

Uninstall an application Uninstalls an application from your company or a specific location. This will remove the application`s access and stop all its functionalities Endpoint: DELETE /marketplace/app/{appId}/installations (Version header: v3; source: v3/marketplace-v3.json) Requires an Agency or Sub-Account token. OAuth access token only — Private Integration Tokens are rejected. OAuth scopes: oauth.write

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": {
      "appId": "<appId>",
      "body": "<body>"
    },
    "name": "ghl_marketplace_uninstall_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
appIdYesThe application id which is to be uninstalled.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"DeleteIntegrationBodyDto"
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, yet the description still adds real value: 'This will remove the application`s access and stop all its functionalities' states the concrete consequence, and the token/scope constraints disclose auth requirements not present in annotations. It stops short of describing irreversibility or a response, but this is solid added context.

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?

Front-loaded with the action and its consequence, then prerequisites; most sentences earn their place. Minor waste in the first line restating the title verbatim and in the 'stop all its functionalities' clause overlapping the preceding sentence.

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 destructive, no-output-schema mutation this covers the essentials: endpoint/version, required token type, OAuth scope, and the effect of uninstalling at agency vs. location level. The agency-vs-location semantics are left to the schema rather than restated, which is acceptable given 100% coverage.

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 the nested body fields (reason, companyId, locationId) and appId are already fully documented in the schema, including the token-conditioned requirements. The description adds no syntax, format, or conditional logic beyond what the schema provides, so the baseline of 3 applies.

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 opens with a specific verb and resource ('Uninstalls an application') and scopes it to 'your company or a specific location'. It is unambiguous and there is no sibling that could be confused with an uninstall operation, though it never explicitly differentiates itself from adjacent marketplace tools (installer details, migrate connection).

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?

Gives clear preconditions: requires an Agency or Sub-Account token, OAuth access token only, Private Integration Tokens rejected, scope oauth.write. That is actionable context about when the tool is callable, but there are no explicit 'do not use for X' exclusions or pointers to alternative marketplace tools.

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