Skip to main content
Glama

Update Magic Audience Ad

update_magic_audience_ad

Update a Magic Audience ad object under a campaign. 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>",
      "campaignId": "<campaignId>",
      "adId": "<adId>"
    },
    "name": "update_magic_audience_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
adIdYesMagic Audience (Magic Ads) ad ID.
adNameNoName of the ad.
statusNoStatus value; use one of the allowed values in this schema.
adFormatNoAd format; use one of the allowed values.
headlinesNoHeadline variants for the ad.
mediaUrlsNo
videoInfoNo
campaignIdYesMagic Audience (Magic Ads) campaign ID.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
descriptionsNoDescription variants for the ad.
primaryTextsNoPrimary text variants for the ad.
isAiGeneratedNo
variantNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / adFormat / description
      Added value: +"Ad format; use one of the allowed values."
    • addedInput schema / properties / adId / description
      Added value: +"Magic Audience (Magic Ads) ad ID."
    • addedInput schema / properties / adName / description
      Added value: +"Name of the ad."
    • addedInput schema / properties / campaignId / description
      Added value: +"Magic Audience (Magic Ads) campaign ID."
    • 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 / descriptions / description
      Added value: +"Description variants for the ad."
    • addedInput schema / properties / headlines / description
      Added value: +"Headline variants for the ad."
    • addedInput schema / properties / primaryTexts / description
      Added value: +"Primary text variants for the ad."
    • addedInput schema / properties / status / description
      Added value: +"Status value; use one of the allowed values in this schema."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description usefully adds the authorization gate, grace-period warning display, and an absolute stop condition. However, it omits core mutation behavior: whether this is a partial patch (unset fields preserved) or a full replace, and the schema's status enum includes DELETED, so an agent could effectively remove the ad despite destructiveHint=false with no warning in the description.

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 and the sentences are readable, but the access-control block is repetitive: "check business permissions," "Call check_business_tool_access before collecting inputs," and "never proceed when access is blocked" restate the same gate three times. The redundancy crowds out room for update semantics that are actually missing.

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?

For a 13-parameter mutation tool with no output schema, the permission gating is thoroughly covered, but the definition omits what an update actually does to unspecified fields, what a success response looks like, and that status=DELETED removes the ad. Adequate on access policy, incomplete on operation semantics.

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 says nothing about any of the 13 parameters, and schema coverage is only 69% — mediaUrls, videoInfo, isAiGenerated, and variantNumber carry no description in either place. With no explanation of required vs. optional nesting, field interaction (e.g., videoInfo vs. mediaUrls for SINGLE_VIDEO), or partial-update semantics, the description leaves the caller dependent on an incomplete schema.

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?

"Update a Magic Audience ad object under a campaign" gives a specific verb, resource, and parent scope, which cleanly separates it from create_magic_audience_ad, get_magic_audience_ad, and update_magic_audience_campaign. It never names a sibling to contrast against, so the differentiation is inferred from the verb rather than stated.

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?

Strong precondition guidance: it mandates calling check_business_tool_access before collecting inputs, states an explicit exclusion (FREE businesses cannot use this tool regardless of feature rows), and says never to proceed when access is blocked. It does not contrast update vs. create/get/delete for this resource, so the alternative-selection guidance is narrower than a 5 would require.

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