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

ghl-mcp-server-v2

by zackscriven

ghl_estimate_send

Sends a GoHighLevel estimate by its ID so you can deliver it via email, SMS, or manually using the specified location and authorized user details.

Instructions

Send Estimate API to send estimate by estimate id Endpoint: POST /invoices/estimate/{estimateId}/send (Version header: v3; source: v3/invoices-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: invoices/estimate.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": {
      "estimateId": "<estimateId>",
      "body": "<body>"
    },
    "name": "ghl_estimate_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
estimateIdYesEstimate Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / sentFrom / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "fromEmail": {
      -        "description": "Email id to be used while sending email notification",
      -        "example": "alex@example.com",
      -        "type": "string"
      -      },
      -      "fromName": {
      -        "description": "Sender name to be used while sending email notification",
      -        "example": "Alex",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "fromEmail": {
      +        "description": "Email id to be used while sending email notification",
      +        "example": "alex@example.com",
      +        "type": "string"
      +      },
      +      "fromName": {
      +        "description": "Sender name to be used while sending email notification",
      +        "example": "Alex",
      +        "type": "string"
      +      }
      +    },
      +    "title": "InvoiceSettingsSenderConfigurationDto",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / title
      Added value: +"SendEstimateDto"
  2. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare non-readonly, open-world, non-idempotent, non-destructive, but the description goes beyond them by naming the auth model and OAuth scope, which annotations do not carry. The main omission is that sending actually dispatches email/SMS to the recipient (per the body 'action' field), a consequential side effect that isn't stated.

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 verb and resource, then constrained to endpoint and auth lines. The endpoint/provenance line is metadata padding for an agent's decision-making, but overall it is short and waste-free.

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?

The schema fully describes the nested request body, so parameter detail is covered. Still, for a mutation tool with real-world outbound communication and no output schema, the description should note what sending triggers and what a success response looks like; without that, it is adequate but not 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 description coverage is 100% and the nested SendEstimateDto documents altId, userId, liveMode and sentFrom in detail. The description only restates that the operation keys on estimateId, adding no semantics about the action/sms-vs-email choice or liveMode beyond the schema, so baseline 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?

States a specific verb and resource ('send estimate by estimate id') with the exact endpoint, so the agent knows precisely what operation runs. It is distinguishable from ghl_estimate_update/create/convert_to_invoice, but it never explicitly contrasts itself with ghl_invoice_send, which has a near-identical shape.

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 token requirement ('Agency or Sub-Account token') and OAuth scope give preconditions for calling, which is real usage context. However, there is no explicit when-to-use/when-not guidance and no mention of when an agent should prefer ghl_invoice_send or another delivery path.

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