Skip to main content
Glama

ADS Beast

analytics_ab_tests

Read-only

A/B tests with their status and interim results.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analytics_ab_tests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax records.
statusNoOnly records in this status.
client_idNo
campaign_idNoADS Beast id from list_campaigns, not the platform's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. Beyond that the description adds only 'interim results', with no mention of pagination behavior, what limit defaults to, whether results are partial for running tests, or how many tests are typically returned.

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?

It is a single short sentence fragment with no wasted words, but it is under-specified rather than concise — there is no subject or verb and no second sentence to establish scope or filtering behavior.

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?

With four parameters, no output schema, and an open-world read, the description should say what a returned A/B test record contains (status values, interim metrics) and how filtering by client_id/campaign_id behaves. None of that is present, leaving the agent dependent entirely on the schema.

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 75%, so the schema already documents limit, status and campaign_id, and the description adds nothing further. The one undocumented parameter, client_id, gets no explanation in either place; the description could have noted that it scopes results to a single client.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'A/B tests with their status and interim results' identifies the resource (A/B tests) and hints at returned attributes, but omits the verb entirely — an agent must infer from the title/annotations that this lists rather than creates or analyzes. It also fails to distinguish itself from the sibling ab_test_create.

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?

There is no when-to-use guidance at all: no statement of when to call this versus ab_test_create, analytics_attribution, or analytics_summary. The only implied usage comes from the enum on 'status', which suggests filtering, not tool selection.

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.