Skip to main content
Glama

Regenerate Creative Asset

regenerate_creative_asset

Regenerate a product creative 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": "regenerate_creative_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYesCreative asset or Magic Content asset ID.
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 / 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."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety is partly covered; the description adds genuinely new access-gating behavior (business-tier blocking, grace-period warnings, resubscribe links). However, it says nothing about what happens to the original asset, whether regeneration consumes credits, or whether it is idempotent — material gaps for a mutation tool.

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 in the first sentence, which is good, but the remaining text is a dense permission checklist that repeats the same temporal constraint three times ('before offering', 'before collecting inputs', 'before continuing'). The gating policy crowds out the core operation.

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?

For a two-parameter mutation with no output schema, the access prerequisites are covered thoroughly, but an agent still cannot tell what the call returns or what state change to expect. Adequate on process, incomplete on outcome.

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 (assetId, communityId) are documented in the schema, including the communityId provenance warning, so the baseline of 3 applies. The description's only parameter-adjacent remark ('requesting its inputs') adds no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Regenerate a product creative asset'), which is better than a tautology, but it never explains what regeneration actually produces (a new asset, a new asset ID, or an in-place overwrite) or how it differs from the sibling edit_creative_asset. An agent can name the action but not predict its result.

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 concrete when-not conditions ('FREE businesses cannot use this tool, regardless of individual feature rows') and a mandatory prerequisite ('Call check_business_tool_access before collecting inputs'). It lacks guidance on choosing this over edit_creative_asset or import_creative_asset, so it falls short of a 5.

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