Metadata MCP Connector

Restart Experiment Keyword

restart_experiment_keyword

Destructive

Restart a specific paused keyword in an experiment.

            PURPOSE:
            Restart a keyword that was previously paused in an experiment. This re-enables the keyword
            so it starts running again in the specified experiment.

            SCOPE - THIS TOOL ACTS ON ONE KEYWORD, NOT ON THE EXPERIMENT:
            It restarts a SINGLE keyword INSIDE an experiment. It cannot restart a paused
            experiment. To pause or restart a WHOLE experiment, use manage_experiment instead.

            WHEN TO USE:
            - Restart a keyword that was previously paused in an experiment
            - Re-enable a keyword after resolving performance issues
            - Resume keyword activity in a specific experiment

            PREREQUISITE:
            Use list_experiment_keywords first to find the keywordExternalId and wizExperimentId
            for the keyword you want to restart. Both come from that tool's results:
            keywordExternalId identifies the keyword on the ad channel, and wizExperimentId
            is the experiment's ID (the same ID search_experiments returns as experimentId).

            WORKFLOW:
            1. Search for the keyword: list_experiment_keywords(keywordOrExperimentName="my keyword")
            2. Note the keywordExternalId and wizExperimentId from the results
            3. Restart it: restart_experiment_keyword(keywordExternalId=12345, wizExperimentId=678)
            4. (Optional) Verify later: list_experiment_keywords(keywordOrExperimentName="my keyword")
               to check the status has changed

            PARAMETERS:
            - keywordExternalId: Required. The external ID of the keyword to restart (from list_experiment_keywords).
            - wizExperimentId: Required. The experiment ID where the keyword is running (from list_experiment_keywords).

            WARNING: This action changes the state of the keyword in the experiment.
            The keyword will resume running in the specified experiment.

            WARNING: ASYNC FLOW: Restarting a keyword is an asynchronous operation. The status change
            may not be immediately reflected. Use list_experiment_keywords after some time
            to verify the keyword status has been updated.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`wizExperimentId`	Yes	The experiment ID where the keyword is running.
`keywordExternalId`	Yes	The external ID of the keyword to restart.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already signal mutation with destructiveHint=true and readOnlyHint=false, so the bar is lower. The description adds valuable context beyond annotations: the operation is asynchronous, status changes may be delayed, and verification via list_experiment_keywords is recommended.

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 description is well-structured with sections, but it contains redundancy: the PURPOSE section restates the opening sentence, the WHEN TO USE bullets repeat the same idea, and the PARAMETERS section duplicates the schema. It is useful but not every sentence earns its place.

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?

For a state-changing tool with no output schema, the description is highly complete: it covers prerequisites, identifier sourcing, workflow, async behavior, verification steps, and a clear exclusion for whole-experiment operations. An agent has enough information to invoke the tool correctly.

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 100%, so the schema already documents both parameters. The description adds meaning by explaining where to obtain both IDs (keywordExternalId and wizExperimentId from list_experiment_keywords) and clarifies which ID identifies the keyword versus the experiment.

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 opens with a specific verb and resource: 'Restart a specific paused keyword in an experiment.' It also clearly scopes the tool to a single keyword inside an experiment and explicitly distinguishes it from manage_experiment, which handles whole experiments.

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?

It provides explicit 'WHEN TO USE' bullets, a prerequisite workflow, and names the alternative tool for whole-experiment operations. The description also tells the agent to use list_experiment_keywords first and how to verify the restart afterward.

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

All Metadata MCP Connector tools Inspect

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

Need Help?