Skip to main content
Glama

Generate Magic Content From Scratch

generate_magic_content_from_scratch

Generate Magic Content directly from a creative direction. 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>",
      "assetType": "<assetType>",
      "creativeDirectionPrompt": "<creativeDirectionPrompt>"
    },
    "name": "generate_magic_content_from_scratch"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
productTypeNoType of the product the asset is for.
imageSettingsNo
videoSettingsNo
entityObjectIdNoObject ID of the product or entity this action targets.
creativeDirectionPromptYesCreative direction for the generated or edited asset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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 / 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."
    • addedInput schema / properties / productType / description
      Added value: +"Type of the product the asset is for."
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The description adds substantial behavioral context beyond annotations: generation is gated by business permissions, FREE businesses are excluded regardless of feature rows, and blocked access must stop the workflow. It does not describe cost, generation latency, or any side effects of creating content, but the permission behavior is disclosed in useful detail.

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?

The purpose is front-loaded and the remaining sentences focus on mandatory access gating. There is some repetition between 'before offering this action or requesting its inputs' and 'before collecting inputs', but the wording is dense and mostly earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter generation tool with no output schema, the definition covers access gating well but leaves core invocation details thin. It does not explain return behavior, how attachments or image/video settings affect generation, or how the tool differs from related generation tools.

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 mentions a creative direction and says inputs should not be collected before checking access, but it adds no meaning for the other parameters such as communityId, assetType, attachments, imageSettings, videoSettings, productType, or entityObjectId. With only 63% schema description coverage and several undocumented optional fields, the description does not compensate for the missing parameter semantics.

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 states a clear verb and resource: generate Magic Content directly from a creative direction. The phrase 'from scratch' hints at fresh generation, but it does not explicitly differentiate this tool from sibling generate_magic_content or explain when fresh generation is preferred over other generation flows.

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 gives strong usage constraints: check business permissions first, call check_business_tool_access before collecting inputs, and never proceed when access is blocked. It clearly states FREE businesses cannot use the tool and requires surfacing grace-period warnings, but it does not compare this tool with alternative generation tools such as generate_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