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

ghl-mcp-server-v2

by zackscriven

ghl_social_csv_list

Read-onlyIdempotent

Lists the status of all CSV bulk-import batches for a GoHighLevel location, with skip/limit pagination and optional user/template filters. Use it to review import progress and outcomes.

Instructions

Lists the status of ALL CSV bulk-import batches for the location (operationId get-upload-status — the name is misleading; it's a paginated list, not a single status check). Supports skip/limit; userId query param is required per spec. Get Upload Status Get the status of all CSV imports for a location Endpoint: GET /social-media-posting/{locationId}/csv (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/csv.readonly Pagination params: skip, limit — 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": {
      "locationId": "<locationId>",
      "userId": "<userId>"
    },
    "name": "ghl_social_csv_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of records to skip0
limitNoMaximum number of records to return10
userIdYesUser ID
locationIdYesLocation ID (also known as Sub-Account ID) for the business location.
includeUsersNoInclude user data in response
isFromTemplateNoFilter CSVs imported from template library

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.1.0
    • addedInput schema / properties / includeUsers / example
      Added value: +"true"
    • addedInput schema / properties / limit / example
      Added value: +"10"
    • changedInput schema / properties / locationId / description
      Previous value: -"Location Id"New value: +"Location ID (also known as Sub-Account ID) for the business location."
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
    • addedInput schema / properties / skip / example
      Added value: +"1"
    • changedInput schema / properties / userId / example
      Previous value: -"ve9EPM428h8vShlRW1KT"New value: +"sdfdsfdsfEWEsdfsdsW32dd"
  2. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, and the description adds genuinely new operational detail: requires a Sub-Account (location) token, OAuth scope socialplanner/csv.readonly, the endpoint and v3 version header, and pagination behavior. It doesn't describe the shape or fields of returned batches, which keeps it below a 5.

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 first sentence is well front-loaded and high value, but the tool then repeats itself with 'Get Upload Status' and 'Get the status of all CSV imports for a location', which duplicate the opening claim. Endpoint/version/source metadata is boilerplate that inflates length without helping selection.

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?

With no output schema, the description still conveys that the return is a list of import batches with status, and it covers auth, scoping, and pagination — the things an agent needs to call it correctly. It could say more about what fields each batch carries, but the essentials are present.

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 100% with descriptions and examples for every parameter, so the schema already carries the semantic load. The description reinforces that skip/limit are pagination controls and that userId is required, but says nothing about includeUsers or isFromTemplate, so it adds only marginal value beyond the schema.

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?

States a specific verb and resource (lists CSV bulk-import batches) plus scope (ALL batches for the location), and explicitly disambiguates from the misleading operationId 'get-upload-status' by clarifying it is a paginated list, not a single status check. An agent can distinguish it from ghl_social_get_csv_post and ghl_social_csv_upload without opening any schema.

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 operational context: it is a paginated list, skip/limit should be passed to page through full result sets, and userId is required per spec. It does not explicitly name sibling alternatives (e.g. ghl_social_get_csv_post for a single import), so it stops short of full when-to-use/when-not guidance.

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