Nas.com

Export Business Members

export_business_members

Read-only

Export members for a managed community using the manager member filters. 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": "export_business_members"
  }
}

Input Schema

Name	Required	Description
`role`	No
`pageNo`	No	Page number to return, starting at 1.
`sortBy`	No	Field to sort results by.
`status`	No	Status value; use one of the allowed values in this schema.
`segment`	No
`fileName`	No
`pageSize`	No	Number of results per page.
`sortOrder`	No	Sort direction for the results.
`communityId`	Yes	Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
`searchString`	No	Text to search for.
`withApplication`	No
`selectedMembershipTiers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 10, 2026

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 / 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."

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), and the description adds real behavioral context on top: plan-tier blocking for FREE businesses, a mandatory permission gate, and grace-period/resubscribe handling. It stops short of describing what the export produces (file vs. inline results, sync vs. async) which matters for a tool with a fileName parameter.

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?

Purpose is front-loaded in the first sentence, followed by prerequisites in a logical order. There is mild redundancy between 'check business permissions', 'Call check_business_tool_access before collecting inputs', and 'never proceed when access is blocked', but the repetition is defensible for a gating instruction.

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?

For a 12-parameter, no-output-schema export tool, the definition covers access gating thoroughly but leaves the mechanics underspecified: what the export returns, how fileName affects delivery, and how the secondary filters behave. An agent can decide whether it is allowed to call the tool but not fully predict what it will get back.

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 58% across 12 parameters, so several fields (role, segment, fileName, withApplication, selectedMembershipTiers) carry no meaning in either place. The description only mentions 'manager member filters' generically and adds nothing about paging, sorting, or file naming, so it does not compensate for the coverage gap.

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 ('Export members for a managed community') and clarifies the business/community terminology overlap, which is genuinely useful for an agent mapping sibling names. It does not, however, distinguish itself from export_community_members or list_business_members_for_admin, so differentiation 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?

Gives strong explicit preconditions: check business permissions first, call check_business_tool_access before collecting inputs, FREE businesses cannot use it regardless of feature rows, surface grace-period warnings, and never proceed when access is blocked. What is missing is guidance on when to choose this export over the sibling export/list tools for members.

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

All Nas.com tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.