Skip to main content
Glama

Metadata MCP Connector

Search Experiments

search_experiments
Read-only

Search for experiments (ad sets) by name, status, and budget group with flexible filtering. adIds lists an experiment's ads without their status, and the SOME_ADS_INACTIVE issue does not say which ads are off: call list_experiment_ads with the experimentId for each ad's status in the ad set.

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
pageNoPage number for pagination (default: 0)
sizeNoNumber of results per page (default: 5)
sortNoSort criteria in format 'field,direction' (e.g., 'name,asc')
search_nameNoThe experiment or campaign name to search for (partial, case-insensitive matching). Optional - omit to skip name filtering.
budget_group_idsNoOptional array of budget group IDs to filter experiments. Only returns experiments that belong to these budget groups.
launched_experiment_statusesNoOptional array of experiment statuses to filter by. Valid values: Active, WithoutSpend, Paused, Completed, Failed, Disconnected

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses that adIds is returned without status and that the SOME_ADS_INACTIVE issue does not identify which ads are off, which is a subtle result-shape limitation an agent could not infer from annotations or schema.

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 purpose is front-loaded in a single efficient sentence, but the second sentence is a dense run-on ('call list_experiment_ads with the experimentId for each ad's status in the ad set') that is grammatically tangled and mixes result interpretation into a search definition. The information earns its place but the phrasing is not clean.

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

Completeness4/5

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

With no output schema, the description usefully compensates by explaining what the adIds field contains and what the SOME_ADS_INACTIVE issue does and does not mean, plus the remediation path. Pagination and sorting are left to the schema, which is reasonable, so only minor gaps remain.

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 100%, so all six parameters including search_name, budget_group_ids, and launched_experiment_statuses are already documented in the schema. The description only restates the filter dimensions ('by name, status, and budget group') and adds no matching semantics, format, or default behavior beyond what the schema supplies, so the baseline 3 applies.

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 first sentence gives a specific verb and resource ('Search for experiments (ad sets)') plus the filterable fields (name, status, budget group), and disambiguates the term 'experiments' as ad sets. It does not, however, distinguish this tool from name-adjacent siblings such as search_campaigns_by_names, so an agent cannot fully route on the description alone.

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 guidance is present but narrowly scoped: it tells the agent to call list_experiment_ads with an experimentId when ad status is needed, which is a follow-up rule rather than a selection rule for this tool. There is no explicit when-to-use or when-not-to-use guidance relative to other search tools.

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