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

ghl-mcp-server-v2

by zackscriven

ghl_company_get

Read-onlyIdempotent

Retrieve detailed company information using an agency-level token and company ID. Fetches company data via the GoHighLevel API for management and reporting.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Get Company Get Comapny Endpoint: GET /companies/{companyId} (Version header: v3; source: v3/companies-v3.json) Requires an Agency (company-level) token. OAuth scopes: companies.readonly

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": {
      "companyId": "<companyId>"
    },
    "name": "ghl_company_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 already cover read-only, idempotent and open-world behaviour, so the description is not obligated to restate safety. It adds genuinely new operational context: agency-access-only security, the exact OAuth scope, the v3 version header, and the endpoint path — all of which affect whether a call succeeds.

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 auth requirement is front-loaded, which is good, but the content is padded: the same token requirement is stated twice (opening sentence and penultimate sentence), and 'Get Company' / 'Get Comapny' are redundant, typo-ridden restatements of the title.

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 single-resource read with one parameter and no output schema, the definition covers the essentials an agent needs: endpoint, auth tier, scope, and the path parameter. The main gap is that with no output schema and no return description, the agent cannot anticipate the shape of the company object returned.

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 0%, so the description has to carry the load: it does show companyId as a path segment in GET /companies/{companyId}, clarifying that it identifies the agency/company resource. However, it never explains the format or where an agent would obtain a valid companyId, and the schema itself offers only an opaque example string.

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 states a specific verb+resource (GET /companies/{companyId}) and makes clear it retrieves a single company record, which is distinct from the many calendar/contact siblings. It does not explicitly contrast with near-neighbours like ghl_business_get or ghl_saas_get_locations, and the duplicated typo line 'Get Comapny' adds noise rather than clarity.

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 gives a real prerequisite — an agency-level/Company token and the companies.readonly scope — which tells the agent when the call is even permissible. But there is no guidance on when to prefer this over other company/location lookups, and no statement of failure modes (e.g., what happens with a location-level token).

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