Skip to main content
Glama

List Magic Content Versions

list_magic_content_versions
Read-only

List versions for a Magic Content asset. 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>",
      "assetId": "<assetId>"
    },
    "name": "list_magic_content_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number to return, starting at 1.
assetIdYesCreative asset or Magic Content asset ID.
pageSizeNoNumber of results per page.
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. Changed4 schema fields changed
    • addedInput schema / properties / assetId / description
      Added value: +"Creative asset or Magic Content asset ID."
    • 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.6/5.0
Behavior3/5

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

Annotations already declare it a safe, non-destructive read, so the description's contribution is the access-gating behavior: tier-based blocking, grace-period warnings, and a requirement to surface a resubscribe link. That is useful context beyond the annotations, but nothing is said about result ordering, version semantics, or pagination defaults.

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 is front-loaded in the first sentence, which is good. However, four of the five sentences are permission boilerplate, and the closing "never proceed when access is blocked" restates the blocking already established two sentences earlier, so there is measurable redundancy.

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 read-only paginated list tool with full schema coverage and no output schema, the definition covers what an agent most needs to know before calling: the access prerequisite and tier restriction. It is only short on what a 'version' represents and how the returned version IDs are consumed downstream.

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%, so all four parameters (communityId, assetId, pageNo, pageSize) are already documented with constraints in the schema. The description only implies that assetId refers to a Magic Content asset and adds no format or usage detail beyond that, 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?

"List versions for a Magic Content asset" is a specific verb plus resource that separates this from list_magic_contents (assets) and from the mutation siblings like edit_magic_content. It does not explicitly name the sibling it complements, but the resource scope is unambiguous.

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?

It states an explicit hard exclusion ("FREE businesses cannot use this tool, regardless of individual feature rows") and a mandatory prerequisite step ("Call check_business_tool_access before collecting inputs"), which is real when-to-use/when-not guidance. What it lacks is any guidance on when to reach for this versus list_magic_contents or get_magic_content.

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