Skip to main content
Glama

List Products

list_products
Read-only

List unified products for a community managed by the authenticated Nas.com user. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>"
    },
    "name": "list_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number to return, starting at 1.
sortByNoField to sort results by.
statusNoStatus value; use one of the allowed values in this schema.
pageSizeNoNumber of results per page.
sortOrderNoSort direction for the results.
priceTypesNo
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
productTypeNoType of the product the asset is for.
searchStringNoText to search for.
timingStatusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / pageNo / description
      Added value: +"Page number to return, starting at 1."
    • addedInput schema / properties / pageSize / description
      Added value: +"Number of results per page."
    • addedInput schema / properties / productType / description
      Added value: +"Type of the product the asset is for."
    • addedInput schema / properties / searchString / description
      Added value: +"Text to search for."
    • addedInput schema / properties / sortBy / description
      Added value: +"Field to sort results by."
    • addedInput schema / properties / sortOrder / description
      Added value: +"Sort direction for the results."
    • addedInput schema / properties / status / description
      Added value: +"Status value; use one of the allowed values in this schema."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds genuinely non-obvious behavioral context about the mandatory entitlement gate and the grace-period/resubscribe warning flow. It says nothing about pagination defaults, result volume, or ordering behavior beyond what the schema implies.

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 purpose is front-loaded in one sentence, but the access-check instruction is then restated twice ('check business permissions ... Call check_business_tool_access before collecting inputs'), and the grace-period/resubscribe sentence is dense. Roughly half the text is redundant with itself.

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 a read-only list tool with no output schema and 80% schema coverage, the description is nearly complete: the entitlement gate is the main non-schema risk and it is fully covered. What is missing is only guidance on how filtering/sorting parameters combine, which the schema partly handles.

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 80%, so the schema carries most parameter meaning and baseline 3 applies. The description adds no filter semantics at all and does not clarify the loosely documented parameters (priceTypes, timingStatus, productType) that have only minLength constraints.

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 first sentence gives a specific verb and resource ('List unified products') scoped to a community owned by the authenticated Nas.com user, which is enough to distinguish it from the many specialized product lists (upsell, discount, top-selling). It stops short of explicitly contrasting with those siblings, so an agent must infer the 'unified/all products' scope on its own.

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?

Strong precondition guidance: it names the prerequisite tool (check_business_tool_access), states an explicit exclusion (FREE businesses cannot use this tool regardless of feature rows), and says not to proceed when access is blocked. The gap is selection guidance among alternative product-list siblings, which is never addressed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources