Metadata MCP Connector

Update Experiment End Date

update_experiment_end_date

Destructive

Move the end date of ONE running Google Ads or Microsoft Ads experiment, leaving the campaign's other experiments as they are.

            KEYWORDS: experiment, end date, extend, shorten, schedule, stop date, run until

            WHEN TO USE:
            - User wants experiment X to run until a later or earlier date
            - User wants to change one experiment's end date without touching the rest of its campaign

            WHAT THE PLATFORM ALLOWS:
            - Google Ads and Microsoft Ads experiments that are running (Active): this tool.
            - A Completed experiment, any channel: manage_experiment(action="reactivate",
              end_date=...), which runs it again until that date.
            - A LinkedIn, Facebook, Instagram or Reddit experiment: the platform moves its
              end date only campaign-wide (add_and_edit_campaign_elements or
              add_and_edit_native_campaign_elements, which move every experiment of that
              campaign). This tool refuses them and changes nothing.
            - A Paused experiment: its end date moves only while it runs; restart it
              (manage_experiment) only if the user wants it running again.
            - Google Ads re-applies the experiment's saved countries and states with the
              date, so the tool refuses Performance Max, an experiment that excludes
              locations, and one with no saved countries or states.

            PARAMETERS:
            - experiment_id: experimentId from search_experiments
            - end_date: YYYY-MM-DD, today or later and within a year; the experiment runs
              through that day

            RESULT:
            status="submitted" means the change was sent: the channel applies it in the
            background, and search_experiments shows the new end date once the channel
            confirms. Say it was requested, not that it changed, until a read shows it.
            status="unchanged" means it already ended on that date and nothing was sent.
            success=false comes with an error that says why nothing was changed.

            WARNING: This changes the live schedule of the experiment on the ad channel.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`end_date`	Yes	The new end date, YYYY-MM-DD, today or later and within a year. The experiment runs through that day.
`experiment_id`	Yes	The experiment to change (experimentId from search_experiments).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already flag destructive=true and openWorld=true, but the description goes further: it discloses the asynchronous submit-then-confirm behavior ('Say it was requested, not that it changed, until a read shows it'), the platform-specific refusal cases (Performance Max, excluded locations, no saved countries), and the live-schedule mutation warning.

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?

Front-loaded with the core action and organized under clear headers, so it is scannable despite its length. It is somewhat verbose (repeated keyword list, long refusal enumeration), but for a tool with this many channel/state edge cases most sentences earn their 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?

No output schema exists, so the description compensates by explaining the status='submitted'/'unchanged' and success=false return semantics and the eventual-consistency read path. Combined with the platform-allowance matrix, an agent has everything needed to call and interpret this 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% and both params are documented there, so baseline is 3; the description adds the provenance of experiment_id (experimentId from search_experiments), the inclusive 'runs through that day' semantics, and the today-or-later/within-a-year constraint, all of which reinforce rather than merely repeat the schema.

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?

Opens with a specific verb+resource+scope: 'Move the end date of ONE running Google Ads or Microsoft Ads experiment,' and immediately contrasts with the campaign's other experiments. It is distinguishable from siblings like manage_experiment and add_and_edit_campaign_elements without opening any schema.

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?

Provides an explicit WHEN TO USE list plus a WHAT THE PLATFORM ALLOWS matrix that routes by channel and state (Active vs Completed vs Paused vs LinkedIn/Meta/Reddit), naming the alternative tool for each. It even states which inputs cause a refusal, which is unusually complete routing guidance.

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?