Skip to main content
Glama

ADS Beast

ab_test_create

Register an A/B test in ADS Beast to track its hypothesis and variants. It records the test; it does not change ads.

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": {
      "name": "<name>",
      "hypothesis": "<hypothesis>",
      "what_tested": "<what_tested>",
      "variant_a_name": "<variant_a_name>",
      "variant_b_name": "<variant_b_name>"
    },
    "name": "ab_test_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName shown in the interface.
client_idNo
hypothesisYesIf X then Y changes by Z, because...
campaign_idNoADS Beast id from list_campaigns, not the platform's.
what_testedYesWhat differs between the variants.
variant_a_nameYesControl variant.
variant_b_nameYesTest variant.
variant_a_descriptionNoControl variant in detail.
variant_b_descriptionNoTest variant in detail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds real context beyond that: the tool only records the test and does not modify ads, which tells the agent this write is contained to ADS Beast metadata. It stops short of covering duplicates/idempotency or permission requirements, so it is not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler, and the core action is front-loaded before the important non-mutating caveat. Nothing is wasted or buried.

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 9-parameter write tool with no output schema, the description leaves some gaps: it does not say what the call returns (e.g., a test id), whether client_id or campaign_id are effectively needed, or how this relates to analytics_ab_tests. The high schema coverage compensates for most parameter gaps, making it adequate but not complete.

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 89%, so the schema already explains name, hypothesis, what_tested, and both variant names. The description only echoes 'hypothesis and variants' and adds no format or constraint detail beyond that, which is the expected baseline when the schema does the heavy lifting.

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?

Uses a specific verb and resource: 'Register an A/B test in ADS Beast to track its hypothesis and variants.' This clearly separates it from ad-mutating siblings like prepare_ad_create or create_campaign_draft, though it never names the closest read-side sibling (analytics_ab_tests), so an agent must infer that distinction.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'to track its hypothesis and variants' plus the negative boundary 'it does not change ads.' There is no explicit when-to-use statement, no exclusion of alternatives, and no note on whether the test must already be associated with a client or campaign.

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.