Skip to main content
Glama

List Business Transactions

list_community_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_community_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. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare a safe closed-world read; the description adds substantive behavior the annotations cannot express — plan-tier gating (FREE businesses blocked regardless of feature rows), a mandatory access check, and required surfacing of grace-period warnings and a verified resubscribe link. It does not describe result volume, pagination limits, or date-window constraints beyond what the schema states.

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 statement is front-loaded and clean, but the remainder repeats itself: "check business permissions" and "Call check_business_tool_access before collecting inputs" say the same thing twice, and the UI-flow instructions (show warning, show resubscribe link) are procedural policy rather than tool-selection information.

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

Completeness3/5

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

Access control and plan gating are covered thoroughly, which is the highest-risk failure mode here. But for a tool with 22 mostly undocumented filter parameters and no output schema, an agent gets no help on what the filters mean, how date/page parameters interact, or what the returned transactions contain.

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

Parameters2/5

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

With 22 parameters and only 36% schema description coverage, the description carries the compensation burden but supplies almost nothing — the many filter parameters (transactionType, purchaseType, eventsIds, folderName, subscriptionIntervals, etc.) go entirely unmentioned. The only parameter-related content, the business/community ID equivalence, is essentially a restatement of the communityId schema description.

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?

"List revenue transactions for a community" gives a specific verb and resource, and the business/community interchangeability note resolves a real naming ambiguity for the caller. It stops short of distinguishing this tool from the near-identical list_business_transactions sibling, so an agent still has to guess which variant to pick.

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: check business permissions first, call check_business_tool_access before collecting inputs, FREE businesses are excluded regardless of feature rows, and never proceed when access is blocked. What's missing is any guidance on when to choose this tool over the sibling list_business_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