Skip to main content
Glama

Import Creative Asset

import_creative_asset

Import an image URL as 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>",
      "creativeDirectionPrompt": "<creativeDirectionPrompt>",
      "imageUrl": "<imageUrl>",
      "entityObjectId": "<entityObjectId>",
      "productType": "<productType>"
    },
    "name": "import_creative_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageUrlYesPublic URL of the image to import.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
productTypeYesType of the product the asset is for.
entityObjectIdYesObject 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 / 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 / imageUrl / description
      Added value: +"Public URL of the image to import."
    • addedInput schema / properties / productType / description
      Added value: +"Type of the product the asset is for."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses a gating flow the annotations cannot express: business-tier permission checks, an upstream access-check call, grace-period warning display, and a hard stop when access is blocked. It never states what happens on success (synchronous import vs. queued job) or what is returned, and accepting a public URL sits slightly at odds with openWorldHint=false, though that is a mild tension rather than a contradiction.

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 gating instructions repeat: "check business permissions" and "Call check_business_tool_access before collecting inputs" say the same thing, and "never proceed when access is blocked" restates the FREE-tier prohibition. Roughly one sentence of the four is redundant.

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?

With five required parameters and no output schema, the description covers access gating thoroughly but leaves the outcome undefined: it does not say whether the asset is created synchronously, whether the image is copied or referenced, or what identifier comes back for use with edit_creative_asset or regenerate_creative_asset. That is a real gap for a creation tool with no output schema to fall back on.

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 all five required parameters (imageUrl, communityId, productType, entityObjectId, creativeDirectionPrompt) are already documented, including the "never invent" constraint on communityId. The description adds no parameter-level meaning of its own, so the baseline of 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?

"Import an image URL as a product creative asset" gives a concrete verb (import), a concrete input (image URL), and a concrete output category (product creative asset), which distinguishes it from edit_creative_asset and regenerate_creative_asset by implication. It stops short of an explicit contrast with those siblings, 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?

The description gives a hard when-not rule (FREE businesses cannot use it regardless of feature rows), a named prerequisite tool (check_business_tool_access) with ordering guidance (before collecting inputs), and a blocked-access stop condition. It does not address when to choose this over edit_creative_asset or create_image_asset_upload, leaving the creation-path choice implicit.

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