Skip to main content
Glama

Update Folder Product Indices

update_folder_product_indices

Reorder folder-backed products for a managed community. 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>",
      "folders": "<folders>"
    },
    "name": "update_folder_product_indices"
  }
}

Input Schema

NameRequiredDescriptionDefault
foldersYesDigital products (folders) in their new display order.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / folders / description
      Added value: +"Digital products (folders) in their new display order."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds real value beyond that with entitlement gating, plan-tier restrictions, grace-period warnings, resubscribe links, and a hard stop when access is blocked. It omits what happens to positions of products omitted from the folders array, which is the main behavioral unknown for a reorder operation.

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 purpose sentence is front-loaded and followed by ordered preconditions, so an agent can act in sequence. There is mild redundancy between 'check business permissions,' the check_business_tool_access call, and 'never proceed when access is blocked,' but nothing is wasted enough to hurt.

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?

For a two-parameter mutation tool with full schema coverage and no output schema, the description covers the risky part (access gating and when to abort) thoroughly. It leaves the effect on unlisted products and the response shape unstated, which is a modest gap.

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 100% and both parameters are documented in the schema, including the folders array as 'new display order' and the communityId sourcing rule. The description adds no meaning about index semantics (relative vs absolute position) beyond what the schema already says, so the baseline 3 applies.

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: 'Reorder folder-backed products for a managed community,' which is distinguishable from siblings like update_folder_product or reorder_folder_items by the explicit 'reorder' action on products. It stops short of naming a sibling to contrast against, so a 4 rather than a 5.

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 unusually explicit when-not guidance: FREE businesses cannot use it, and check_business_tool_access must be called before collecting inputs. It does not clarify when to prefer this bulk reorder over update_folder_product for a single product, so the alternative-selection guidance is incomplete.

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