Skip to main content
Glama

SplitLaunch

by dev.splitlaunch
OverviewDiscussionsAdmin

experiments_update

Partially update an existing experiment and return the updated experiment. Send only fields that should change; use experiments_set_status for lifecycle changes. Plus and Go cannot set URL pattern rules, and Go cannot set geo or traffic-source filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
projectIdNoOptional project ID. Omit only when the API key is project-scoped or the account has a clear default project.
targetingNoOptional targeting object. Device and visitor targeting are available on all plans; trafficFilters and geoFilters require Plus or Pro. Use documented pixel metadata keys such as utm_source, utm_medium, utm_campaign, device, browser, or geo fields.
controlUrlNoReplacement control URL. Omit to keep the current value.
experimentIdYesExperiment ID returned by experiments_create or experiments_list.
variationUrlNoReplacement variation URL. Omit to keep the current value.
urlPatternRulesNoOptional Pro-only URL pattern rules for advanced matching across multiple paths. Prefer simple controlUrl/variationUrl first.
trafficAllocationNoReplacement variation share. Accepts 0-1 or 0-100.
preserveRedirectParamsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / controlUrl / description
      Added value: +"Replacement control URL. Omit to keep the current value."
    • addedInput schema / properties / experimentId / description
      Added value: +"Experiment ID returned by experiments_create or experiments_list."
    • changedInput schema / properties / targeting / description
      Previous value: -"Optional exact-match targeting filters. Use only documented pixel metadata keys such as utm_source, utm_medium, utm_campaign, device, browser, or geo fields when available."New value: +"Optional targeting object. Device and visitor targeting are available on all plans; trafficFilters and geoFilters require Plus or Pro. Use documented pixel metadata keys such as utm_source, utm_medium, utm_campaign, device, browser, or geo fields."
    • addedInput schema / properties / trafficAllocation / description
      Added value: +"Replacement variation share. Accepts 0-1 or 0-100."
    • changedInput schema / properties / urlPatternRules / description
      Previous value: -"Optional URL pattern rules for advanced URL matching. Prefer simple controlUrl/variationUrl first."New value: +"Optional Pro-only URL pattern rules for advanced matching across multiple paths. Prefer simple controlUrl/variationUrl first."
    • addedInput schema / properties / variationUrl / description
      Added value: +"Replacement variation URL. Omit to keep the current value."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds value by specifying partial update behavior, return of updated object, and plan-specific constraints beyond annotations.

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?

Three sentences, front-loaded with purpose, then usage tip and plan limitations. No fluff, every sentence earns its place.

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?

Covers basic behavior, return value, and plan restrictions. Lacks explanation of response structure (no output schema), but experiments_get likely provides that context. Adequate for complexity.

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 coverage is high (78%), so baseline is 3. Description adds plan context for urlPatternRules and targeting, but does not elaborate on individual parameters beyond what the schema provides.

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?

Description states 'partially update an existing experiment' with a specific verb and resource, and distinguishes from sibling 'experiments_set_status' for lifecycle changes.

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

Usage Guidelines5/5

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

Explicitly says to use for partial updates, avoid for lifecycle changes (use experiments_set_status), and notes plan limitations (Plus/Go cannot set URL pattern rules; Go cannot set geo/traffic-source filters).

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

All SplitLaunch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources