Skip to main content
Glama

List Magic Contents

list_magic_contents
Read-only

List Magic Content assets 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>"
    },
    "name": "list_magic_contents"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number to return, starting at 1.
pageSizeNoNumber of results per page.
assetTypeNoKind of creative asset, for example image or video.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
productRefsNo
lastObjectIdNo
includeExamplesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / assetType / description
      Added value: +"Kind of creative asset, for example image or video."
    • 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."
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: entitlement gating by business plan, an explicit pre-flight check step, and instructions to surface a grace-period warning and verified resubscribe link. It is silent on result ordering or pagination semantics, so not quite a 5.

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 and the blocking rules are correctly front-loaded. However, two sentences say the same thing: "Before offering this action or requesting its inputs, check business permissions" and "Call check_business_tool_access before collecting inputs." That redundancy costs space in an otherwise short description.

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?

The access-control story is complete and actionable for a gated read tool, and the safety annotations plus schema cover the rest. Missing is any coverage of the lesser-documented parameters or of what the listing returns, which matters at seven parameters with no output schema. Adequate but with clear gaps.

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 description names no parameter and adds no meaning to any of the seven inputs. With schema description coverage at 57%, three parameters (productRefs, lastObjectId, includeExamples) are undocumented in both places, so the description should have compensated and does not. An agent still has to infer what productRefs and includeExamples do.

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 opens with a specific verb+resource: "List Magic Content assets for a managed community." That is unambiguous for an agent scanning names. It does not distinguish this from near-siblings such as batch_get_magic_contents or list_magic_content_versions, so it stops short of 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 strong conditional guidance: check business permissions first, FREE businesses cannot use it "regardless of individual feature rows," and call check_business_tool_access before collecting inputs. This is explicit when/when-not plus a named prerequisite tool. It offers no guidance on choosing between this and other content-listing tools, which keeps it at 4.

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