Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_product_list

Read-onlyIdempotent

Retrieve a paginated list of products for a location, with optional filters by name, category, or store availability.

Instructions

Lists products for a location. (Generated tool name was originally 'ghl_product_list_invoices' — an evident copy-paste artifact unrelated to this operation; corrected here.) List Products The "List Products" API allows to retrieve a paginated list of products. Customize your results by filtering products based on name or paginate through the list using the provided query parameters. This endpoint provides a straightforward way to explore and retrieve product information. Endpoint: GET /products/ (Version header: v3; source: v3/products-v3.json) OAuth scopes: products.readonly Pagination params: limit, offset — pass them to page through full result sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoThe maximum number of items to be included in a single page of results
expandNoName of an entity whose data has to be fetched along with product. Possible entities are tax, stripe and paypal. If not mentioned, only ID will be returned in case of taxes
offsetNoThe starting index of the page, indicating the position from which the results should be retrieved.
searchNoThe name of the product for searching.
storeIdNofetch and project products based on the storeId
sortOrderNoThe order of sort which should be applied for the date
locationIdYesLocationId is the id of the sub-account
productIdsNoList of product ids to be fetched.
collectionIdsNoFilter by product category Ids. Supports comma separated values
collectionSlugNoThe slug value of the collection by which the collection would be searched
includedInStoreNoSeparate products by which are included in the store and which are not
availableInStoreNoIf the product is included in the online store
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds endpoint and OAuth scope details, which is useful but not deep. No contradictions.

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?

The description is concise and front-loaded with the core purpose. The parenthetical about the name artifact is slightly tangential but valuable. Could be slightly more structured, but no fluff.

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?

Given 12 parameters, 1 required, and no output schema, the description provides enough to use the tool: required locationId, optional filters, and pagination. It doesn't describe the return format, but that's acceptable for a list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description highlights important parameters (search, limit, offset) and their purpose, adding context beyond the schema. It doesn't explain all 12 parameters but covers the key ones.

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?

The description clearly states the tool lists products for a location. It differentiates from sibling tools like product_create, product_get, and product_update by focusing on listing. The note about the corrected original name removes confusion.

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?

It explains pagination and filtering by name, and mentions OAuth scopes. However, it doesn't explicitly state when to use this tool over alternatives like ghl_product_search or ghl_product_get, though this is a straightforward list 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/zackscriven/ghl-mcp-server'

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