Nas.com MCP

Create Magic Audience Ad

create_magic_audience_ad

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`adName`	Yes
`status`	No
`adFormat`	Yes
`headlines`	Yes
`mediaUrls`	No
`videoInfo`	No
`campaignId`	Yes
`communityId`	Yes
`descriptions`	Yes
`primaryTexts`	Yes
`isAiGenerated`	No
`variantNumber`	No

TDQS

B3.1/5.0

Behavior3/5

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

The description adds value by disclosing that FREE businesses cannot use the tool and that permission checks are required. However, annotations are minimal and there is no mention of side effects (e.g., creation in Facebook system), reversibility, or output, resulting in a moderate score.

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 description is concise and front-loaded with the primary purpose. The subsequent instructions are well-structured. It could be slightly more streamlined but is effective.

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?

Given the complexity (12 parameters, no output schema, no parameter descriptions), the description is incomplete. It focuses on permissions but lacks details on the actual creation process and parameters, making it insufficient for comprehensive understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description does not explain any parameter meanings. It only states the general purpose, leaving all parameter semantics unexplained. This is a critical gap.

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 clearly states the tool creates a Magic Audience ad object under a campaign, which is specific. However, it does not distinguish from sibling tools like create_magic_audience_campaign or generate_magic_audience_campaign_with_ads, so it loses a point.

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 provides explicit preconditions: check business permissions, call check_business_tool_access, display grace-period warnings. It gives clear steps but does not mention when NOT to use the tool or alternatives, so it is not a 5.

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

All Nas.com MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3/5.0

Disambiguation2/5

Many tools are semantically identical, distinguished only by 'business' vs 'community' prefixes, and descriptions explicitly state they are interchangeable. This creates ambiguity for agent selection. Examples include add_business_admins/add_community_admins and get_business/get_community.

Naming Consistency3/5

Tools generally follow a verb_noun pattern, but the inconsistent use of 'business' vs 'community' for the same entities breaks the pattern. While individual naming is clear, the overall set lacks uniformity.

Tool Count1/5

With 423 tools, the server is massively over-scoped. The high count is driven by redundant 'business' and 'community' variants and many niche operations. A more focused surface would be far more manageable.

Completeness4/5

The tool set covers a broad range of features including CRUD operations for multiple product types, analytics, payments, messaging, and integrations. Minor gaps exist (e.g., missing update for some entity types), but overall domain coverage is strong.

Resources

Need Help?