Skip to main content
Glama

Create Folder Item

create_folder_item

Create an item inside a folder-backed product. 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>",
      "folderId": "<folderId>",
      "type": "<type>",
      "title": "<title>"
    },
    "name": "create_folder_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNo
linkNo
sizeNo
typeYesType value; use one of the allowed values in this schema.
indexNo
titleYesTitle shown to members.
formatNo
statusNoStatus value; use one of the allowed values in this schema.
durationNoTime period for the analytics.
folderIdYesDigital product (folder) ID, from a Nas.com product listing.
platformNoMessaging channel; use one of the allowed values.
thumbnailNo
folderTypeNo
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
descriptionNoDescription shown to members.
signedUrlIdNoSigned upload URL ID returned by the upload URL tool.
isCoverVideoNo
videoObjectIdNo
parentSectionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 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 / description / description
      Added value: +"Description shown to members."
    • addedInput schema / properties / duration / description
      Added value: +"Time period for the analytics."
    • addedInput schema / properties / folderId / description
      Added value: +"Digital product (folder) ID, from a Nas.com product listing."
    • addedInput schema / properties / platform / description
      Added value: +"Messaging channel; use one of the allowed values."
    • addedInput schema / properties / signedUrlId / description
      Added value: +"Signed upload URL ID returned by the upload URL tool."
    • addedInput schema / properties / status / description
      Added value: +"Status value; use one of the allowed values in this schema."
    • addedInput schema / properties / title / description
      Added value: +"Title shown to members."
    • addedInput schema / properties / type / description
      Added value: +"Type value; use one of the allowed values in this schema."
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare it is a non-destructive, closed-world mutation, and the description adds real behavioral context on top: a business-tier eligibility gate, a mandatory pre-flight access check, grace-period warning display, and a hard stop when access is blocked. It does not disclose what state the item is created in (draft vs published) or that file/video types may require a subsequent upload step.

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?

Purpose is front-loaded and the text is short, but the access gating is restated three times ('check business permissions', 'Call check_business_tool_access before collecting inputs', 'never proceed when access is blocked'), which could be compressed into one instruction without losing meaning.

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 19-parameter mutation with no output schema, the description covers only the access gate and says nothing about the actual object being constructed. Given seven enum values for type and several type-specific fields, an agent lacks what it needs to populate inputs correctly.

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?

The schema covers only 47% of 19 parameters, so the description carries a heavy compensating burden and contributes nothing — no explanation of type-dependent parameter requirements, signedUrlId/videoObjectId workflows, index ordering, or folderType. An agent must reverse-engineer the creation flow from enum values alone.

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 description states a specific verb and resource: 'Create an item inside a folder-backed product.' That distinguishes it from create_folder_product (which creates the container) without naming the sibling explicitly. It stops short of telling the agent how it relates to complete_folder_item_upload, which matters for file-type items.

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?

Guidance is explicit and unusually forceful about when NOT to use: FREE businesses cannot use it regardless of feature rows, and the agent must call check_business_tool_access before collecting inputs. What's missing is guidance on choosing this tool over related creation tools such as complete_folder_item_upload or create_folder_product.

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