Skip to main content
Glama
Sign In

Nas.com

by com.nas
OverviewDiscussionsAdmin

Batch Get Creative Assets

batch_get_creative_assets
Read-only

Batch get creative 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>",
      "assetObjectIds": "<assetObjectIds>"
    },
    "name": "batch_get_creative_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
assetObjectIdsYesCreative asset object IDs to fetch in one request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / assetObjectIds / description
      Added value: +"Creative asset object IDs to fetch in one request."
    • 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."
  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 readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds access-control behavior (plan-tier gating, grace-period handling) but says nothing about how the batch behaves on partial failures, invalid IDs, or batch-size limits, which matters for a multi-ID fetch.

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 correctly front-loaded in the first clause, but four of the five sentences are permission preamble that repeats the same idea (check access before doing anything) across FREE-tier, grace-period, and blocked states. It is functional but not tight.

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, read-only batch fetch, the description covers the critical operational risk (entitlement gating) thoroughly. With no output schema, a brief note on what is returned or how missing assets are represented would round it out, but nothing essential is missing to invoke it correctly.

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 description coverage is 100%, so both communityId and assetObjectIds are already documented in the schema, including the warning not to invent IDs. The description adds no additional meaning about the ID list's size limits or ordering, so 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?

The first sentence names a specific verb and resource ('Batch get creative assets') plus a scope ('for a managed community'), which cleanly separates it from batch_get_magic_contents or edit_creative_asset. It stops short of explicitly contrasting with sibling retrieval tools, so it is clear but not fully differentiated.

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 preconditions: call check_business_tool_access before collecting inputs, FREE businesses are excluded regardless of feature rows, surface grace-period warnings, and never proceed when blocked. It does not say when to prefer this over other batch retrieval tools, but the gating guidance is concrete and actionable.

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

All Nas.com toolsInspect
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.

Resources