Nas.com

Create Magic Audience Campaign

create_magic_audience_campaign

Create a Magic Audience / Magic Ads campaign for a managed community. 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>",
      "campaignName": "<campaignName>",
      "entityType": "<entityType>"
    },
    "name": "create_magic_audience_campaign"
  }
}

Input Schema

Name	Required	Description
`adLink`	No
`entityType`	Yes	Type of product or entity this action targets.
`communityId`	Yes	Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
`campaignName`	Yes	Name of the campaign.
`entityObjectId`	No	Object ID of the product or entity this action targets.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 10, 2026

addedInput schema / properties / campaignName / description
```
Added value: +"Name of the campaign."
```

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."

addedInput schema / properties / entityType / description

Added value: +"Type of product or entity this action targets."

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only declare that this is a non-destructive, non-open-world write; the description adds real behavioral context beyond that, namely authorization gating, the FREE-tier exclusion, grace-period warnings, and the verified resubscribe requirement. It stops short of describing what the created campaign's initial state is or whether ads are populated at creation time.

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 front-loaded, but the access gating is restated three times ("check business permissions," "Call check_business_tool_access," "never proceed when access is blocked"), and the grace-period instruction repeats the same idea. Tightening to two sentences would lose nothing.

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

Completeness4/5

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

For a 5-parameter create tool with no output schema, the definition covers the critical prerequisite workflow that an agent would otherwise get wrong. It omits what a successful creation returns or what state the campaign starts in, which is a minor residual gap.

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 80%, so the schema already documents communityId, entityType, entityObjectId, and campaignName. The description adds no parameter-level meaning beyond referring generically to "inputs," so baseline is appropriate.

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 specific verb and resource ("Create a Magic Audience / Magic Ads campaign for a managed community"), which is clear on its own. It does not, however, distinguish this from close siblings such as generate_magic_audience_campaign_with_ads, so an agent must infer the difference from names alone.

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 explicit preconditions: check business permissions first, FREE businesses are excluded regardless of feature rows, and it must not proceed when access is blocked. It does not say when to prefer this over generate/preview siblings, leaving a gap in alternative selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nas.com tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.