Skip to main content
Glama

List Business Transactions

list_business_transactions
Read-only

List revenue transactions for a community managed by the authenticated Nas.com user. Business and community refer to the same thing and are interchangeable. 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_business_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number to return, starting at 1.
searchNoText to search for.
sortByNoField to sort results by.
endDateNoEnd of the reporting window (ISO 8601 date).
pageSizeNoNumber of results per page.
payoutIdNo
eventNameNo
eventsIdsNo
sortOrderNoSort direction for the results.
startDateNoStart of the reporting window (ISO 8601 date).
folderNameNo
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
productsIdsNo
zeroLinkIdsNo
purchaseTypeNo
challengesIdsNo
discountCodesNo
transactionIdsNo
transactionTypeNo
physicalProductIdsNo
subscriptionIntervalsNo
selectedMembershipTiersNo

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 / endDate / description
      Added value: +"End of the reporting window (ISO 8601 date)."
    • 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 / search / 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 / startDate / description
      Added value: +"Start of the reporting window (ISO 8601 date)."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish this as a safe, non-destructive, closed-world read. The description goes beyond them by disclosing access-gating behavior (FREE plan blocking, permission pre-check, grace-period warnings), which is real added value. However, it says nothing about result volume, pagination behavior across the 22 filtering parameters, or what a blocked response looks like beyond 'never proceed'.

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 clean sentence, but the gating instructions restate the same requirement twice ('check business permissions' then 'Call check_business_tool_access before collecting inputs'), and the phrase 'regardless of individual feature rows' is opaque without context. The content earns its place, but the packaging is repetitive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 22-parameter, filter-dense listing tool with 36% schema coverage and no output schema, the description is heavily weighted toward the access-gate workflow and leaves the bulk of the filtering surface undocumented. An agent would know whether it is allowed to call the tool but not how to construct most of the query.

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 only 36%, so roughly fourteen of the 22 parameters — payoutId, eventName, eventsIds, folderName, productsIds, zeroLinkIds, purchaseType, challengesIds, discountCodes, transactionIds, transactionType, physicalProductIds, subscriptionIntervals, selectedMembershipTiers — carry no explanation in either schema or description. The description adds no parameter meaning at all, which leaves a meaningful gap for a filter-heavy tool, though the documented parameters do include pagination and date-window semantics.

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 — listing revenue transactions for a community — and immediately disambiguates the 'business' vs 'community' terminology, which is genuinely useful given siblings named list_business_* and list_community_* that appear parallel. It stops short of distinguishing this tool from list_community_transactions, so the sibling boundary is left implicit.

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?

Unusually explicit about preconditions and exclusions: it names check_business_tool_access as a mandatory prerequisite, declares that FREE businesses cannot use the tool 'regardless of individual feature rows', and specifies the grace-period warning flow. What it lacks is guidance on choosing between this and look-alike siblings such as list_community_transactions.

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