Skip to main content
Glama

Generate Magic Content Prompt

generate_magic_content_prompt

Generate a creative direction prompt for Magic Content. 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>"
    },
    "name": "generate_magic_content_prompt"
  }
}

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.
imageSettingsNo
videoSettingsNo
entityObjectIdNoObject ID of the product or entity this action targets.
styleAssetObjectIdNo
existingAssetObjectIdNo
externalProductObjectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / entityObjectId / description
      Added value: +"Object ID of the product or entity this action targets."
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, which tells the agent nothing about authorization. The description adds substantial behavioral context: entitlement checks are mandatory, a specific sibling must be invoked first, grace-period warnings and a resubscribe link must be surfaced, and blocked access must halt execution. It stops short of describing what the tool actually returns or persists once access is granted.

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 statement is correctly front-loaded and the prose is tight, with no filler sentences. However, four of five sentences are spent on access gating while input usage and output behavior get nothing, so the allocation of space is lopsided for a nine-parameter tool.

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 a tool with nine parameters, no output schema, and a non-read-only annotation profile, the description covers only the authorization gate. An agent still lacks any explanation of what the generated prompt looks like, how the optional asset/settings parameters change output, or what happens after generation — the access-control detail does not compensate for that gap.

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?

Schema description coverage is only 33%, and the description contributes no parameter meaning whatsoever. Seven of nine parameters (attachments, imageSettings, videoSettings, entityObjectId, styleAssetObjectId, existingAssetObjectId, externalProductObjectId) are named but never explained, and the relationship between assetType and the settings objects is left entirely to inference.

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: 'Generate a creative direction prompt for Magic Content.' The word 'prompt' implicitly distinguishes it from siblings that produce finished content, but the description never explicitly contrasts itself with generate_magic_content or generate_magic_content_from_scratch, so an agent must infer which tool actually creates assets.

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 explicit when-not conditions ('FREE businesses cannot use this tool, regardless of individual feature rows'), a prerequisite tool to call first (check_business_tool_access), and a hard stop condition ('never proceed when access is blocked'). What's missing is guidance on when to pick this prompt-generator over the sibling content-generation tools.

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