Skip to main content
Glama

search_experiments

Brands' own A/B tests and which version won. Use it when the user asks what brands tested, which video, text or hook won, or for 'A/B test' or 'split test' results ('did shapewear brands in France test different videos with the same text, and which won?'). A test = ads of one brand launched within 14 days that share one element and differ in another: same video with different texts, same text with different videos (most tests), or same script with a different hook (rare). Each version: its ads with links, launch day, running or stopped, days live, EU reach, and the text that differs, whether the test is clean (only the tested element differs; this compares ad fields, not the video content: right 35 of 40 times in a hand check, so say it), plus a verdict: the version that reached most (with the ratio) when the gap is 2x or more; when the only signal is that one version stopped first, it says so and that this is not a confirmed outcome yet (repeat that). Only tests with a measured outcome are served (a version still running while another stopped, or 2x+ the reach). A summary covers all matching tests per kind (decided by survival, by reach, median reach ratio), shown only from 30 tests of a kind. Costs 5 credits (0 if nothing matches).

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": "search_experiments"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNodefault 10
nicheNoas in search_winners (see filters)
formatNoMeta's display format of the ads tested, e.g. VIDEO, IMAGE
offsetNooffset + limit at most 100: the first 100 results of a query
countryNo2-letter code: tests with an ad reaching that country
with_outcomeNoalways true: only tests with a measured outcome are served

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / offset / description
      Added value: +"offset + limit at most 100: the first 100 results of a query"
    • changedInput schema / properties / offset / maximum
      Previous value: -1000New value: +90
  2. Changed1 schema field changed
    • addedInput schema / properties / format
      Added value: +{
      +  "description": "Meta's display format of the ads tested, e.g. VIDEO, IMAGE",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so extensively: it defines test construction, discloses that only tests with a measured outcome are served, explains verdict rules and the 2x reach threshold, and notes the clean-test heuristic's accuracy. It also states the credit cost, which is important operational context.

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 purpose and usage guidance are front-loaded, and the dense details about test definition, verdict logic, and costs are operationally relevant. The single-paragraph structure and nested parentheticals make it harder to scan, but most sentences earn their place given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain return semantics, and it does: it lists per-version fields such as ads with links, launch day, running status, days live, EU reach, differing text, cleanliness, and verdict. It also covers filtering, cost, and summary behavior, making the definition complete enough for this complex search tool.

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

Parameters4/5

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

Schema coverage is high at 86%, so the schema already documents most parameters. The description adds meaning beyond the schema by explaining the three test kinds (same video/different text, same text/different video, same script/different hook) and by reinforcing the measured-outcome constraint.

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

Purpose5/5

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

The description states a specific resource and outcome: "Brands' own A/B tests and which version won." It also defines what counts as a test and distinguishes this A/B-test focus from generic ad search, so an agent can identify the tool's domain without opening the schema.

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?

It gives clear usage conditions, including example user questions about what brands tested and which video, text, or hook won. It does not explicitly say when not to use this tool or name a sibling alternative, so it falls short of full when/when-not guidance.

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