Skip to main content
Glama

Wavix

by io.github.Wavix

ten_dlc_brand_campaigns_update

Updates a 10DLC Campaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
helpNoIndicates whether the Campaign provides HELP responses
nameNoA user-defined Campaign name
optinNoIndicates whether the Campaign supports opt-in functionality
optoutNoIndicates whether the Campaign supports opt-out functionality
sample1NoMessage sample
sample2NoMessage sample
sample3NoMessage sample
sample4NoMessage sample
sample5NoMessage sample
usecaseNoCampaign use case
brand_idYesBrand ID.
age_gatedNoIndicates whether the Campaign messages contain age-gated content
campaign_idYesCampaign ID.
descriptionNoThe Campaign description
auto_renewalNoIndicates whether the Campaign should be automatically renewed
help_messageNoAn acknowledgement to be sent when a HELP keyword is received
help_keywordsNoA comma-separated list of HELP keywords. The HELP keywords are case-insensitive.HELP
optin_messageNoAn acknowledgement to be sent when an OPT-IN keyword is received
direct_lendingNoIndicates whether the Campaign messages contain direct lending content
embedded_linksNoIndicates whether the Campaign messages contain embedded links
optin_keywordsNoA comma-separated list of OPT-IN keywords. The OPT-IN keywords are case-insensitive.
optin_workflowNoThe opt-in workflow - the process through which consumers opt-in to the Campaign
optout_messageNoAn acknowledgement to be sent when an OPT-OUT keyword is received
privacy_policyNoA link to the Campaign privacy policy
embedded_phonesNoIndicates whether the Campaign messages contain embedded phone numbers
optout_keywordsNoA comma-separated list of OPT-OUT keywords. The OPT-OUT keywords are case-insensitive.
terms_conditionsNoA link to the Campaign terms and conditions
embedded_link_sampleNoAn embedded link sample

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

C2.6/5.0
Behavior1/5

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

No annotations are present, so the description carries the full burden of disclosing behavioral traits. It only states 'Updates a 10DLC Campaign,' with no mention of side effects, partial update semantics, permissions, or idempotency. This is a significant gap for a mutation tool.

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 description is a single sentence with no wasted words, but it is under-specified for a tool with 28 parameters and essential required fields. This is closer to under-specification than effective conciseness.

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 of the tool (28 params, 2 required), the description is too thin. It fails to explain what 'update' entails, which fields are updatable, or how it relates to brand campaigns. An output schema exists but the description provides no additional context.

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?

The input schema has 100% description coverage across all 28 parameters, so the baseline is 3. The tool description adds no extra parameter context; the schema already provides detailed per-parameter descriptions.

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 'Updates a 10DLC Campaign' clearly identifies the action (updates) and the resource (Campaign), distinguishing it from sibling operations like create, delete, get, and list. However, it does not elaborate on the scope or specifics, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not mention when to use this tool, how it relates to other ten_dlc_brand_campaigns_* tools, or any prerequisites such as the need for an existing brand/campaign.

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

All Wavix toolsInspect
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
Disambiguation4/5

Tools are organized by resource with a clear action suffix (create/list/get/update/delete), making most purposes distinct. However, with 122 tools, some pairs like `cdrs_list` vs `cdrs_list_all` or `ten_dlc_brand_campaigns_list` vs `ten_dlc_campaigns_list` could cause confusion without careful reading of descriptions.

Naming Consistency5/5

All tool names follow a consistent `resource_action` snake_case pattern (e.g., `api_keys_create`, `call_control_answer`, `ten_dlc_brands_list`). Verbs are standardized across the set, with only a few exceptions like `check` or `nudge` that still fit the verb-first style. No mixed casing or inconsistent separators.

Tool Count1/5

At 122 tools, this is an extremely large surface that overwhelms the typical MCP agent's ability to select the right tool. Even though the count reflects the full Wavix API, the sheer number far exceeds the 50+ threshold for 'extreme mismatch' and is impractical for most use cases.

Completeness4/5

The tool set covers a broad range of communications features: numbers, calls, messages, billing, CDRs, sub-accounts, 10DLC compliance, speech analytics, and WebRTC. Missing operations like `sub_accounts_delete` or a 2FA service management endpoint are minor gaps that can be worked around via portal or other tools, but overall lifecycle coverage is strong.

Resources