Skip to main content
Glama

Generate Magic Content

generate_magic_content

Generate a Magic Content asset from a selected prompt. 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>",
      "assetType": "<assetType>",
      "creativeDirectionId": "<creativeDirectionId>",
      "creativeDirectionPrompt": "<creativeDirectionPrompt>"
    },
    "name": "generate_magic_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYesCreative asset or Magic Content asset ID.
providerNo
assetTypeYesKind of creative asset, for example image or video.
attachmentsNo
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
imageSettingsNo
videoSettingsNo
entityObjectIdNoObject ID of the product or entity this action targets.
styleAssetObjectIdNo
creativeDirectionIdYesCreative direction ID from the Magic Content prompt or style tools.
creativeDirectionPromptYesCreative direction for the generated or edited asset.
externalProductObjectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / assetId / description
      Added value: +"Creative asset or Magic Content asset ID."
    • 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 / creativeDirectionId / description
      Added value: +"Creative direction ID from the Magic Content prompt or style tools."
    • addedInput schema / properties / creativeDirectionPrompt / description
      Added value: +"Creative direction for the generated or edited asset."
    • addedInput schema / properties / entityObjectId / description
      Added value: +"Object ID of the product or entity this action targets."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false; the description adds genuinely non-obvious behavior: FREE-tier businesses are excluded regardless of feature rows, and grace-period warnings plus a verified resubscribe link must be surfaced. It still says nothing about cost/credits, whether generation is synchronous, or what happens to an existing asset with the same assetId.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, followed by the gating procedure in a logical order. The permission sentences are dense but each carries an operational requirement; only minor redundancy between 'check business permissions' and 'Call check_business_tool_access' could be trimmed.

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?

Access-gating behavior is thorough, which matters for a paid-generation tool, but with 12 parameters, no output schema, and half the schema undocumented, an agent still cannot tell what the optional settings do or what the call returns. Adequate on policy, thin on mechanics.

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?

With 12 parameters at 50% schema description coverage, the description must compensate and does not: it only implies the creative direction prompt is the source. imageSettings, videoSettings, attachments, styleAssetObjectId, entityObjectId, and externalProductObjectId are unexplained in both places.

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?

States a specific verb and resource: 'Generate a Magic Content asset from a selected prompt.' An agent knows the action and its input basis, but nothing distinguishes it from close siblings such as generate_magic_content_from_scratch or generate_magic_content_prompt, which the description never mentions.

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 explicit preconditions: check business permissions, call check_business_tool_access before collecting inputs, never proceed when access is blocked. It lacks any guidance on choosing this tool over the from-scratch or prompt-based variants, so routing between generation siblings is left to inference.

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