Metadata MCP Connector

Unarchive Ad

unarchive_ad

Unarchive (restore) one or more previously archived ads.

                Brings an archived (soft-deleted) ad back to active status. The
                reverse of archive_ad. The ad's id, creative_json, and history are
                preserved across archive/unarchive — same row, status flip.

                USE THIS TOOL WHEN:
                - User asks to restore, unarchive, undelete, recover, reactivate,
                  bring back, or undo the archiving of an ad.
                - User wants to reuse an ad they previously archived.

                HOW TO GET THE id(s) FOR ARCHIVED ADS:
                - Archived ads are NOT returned by `search_ads_by_names` by default
                  (the default `status="active"` filters them out).
                - Call `search_ads_by_names(ad_names=[...], status="archived")` to
                  get ONLY archived ads in the results, then pass the matching ids
                  to this tool. Use `status="all"` if you also want active matches
                  in the same response (rare; usually you want just "archived").
                - get_ad_details(ids=...) works on archived ids too if you already
                  have the id.

                ALSO KNOWN AS: unarchive ad, restore ad, undelete ad, recover ad,
                reactivate ad, bring back ad, undo archive.

                KEYWORDS: unarchive, restore, undelete, recover, reactivate,
                bring back, undo archive, revive, resurrect.

                PARAMETERS:
                - ids: Array of integer ad ids (at least one). Bulk-friendly.

                RETURNS:
                { "success": true, "unarchived_ids": [123, 456], "count": 2 }

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	Yes	Ad id(s) to unarchive. At least one integer required; pass multiple to restore in bulk.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses that the operation is a status flip from archived to active, that the ad's id, creative_json, and history are preserved, and that it is a soft-delete reversal. This goes beyond the annotations (readOnlyHint=false, destructiveHint=false) by clarifying the non-destructive, reversible nature. However, it does not mention any permission prerequisites or potential side effects (e.g., whether it can be applied to ads in any state), so a 4 is appropriate.

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 description is long but well-organized with clear sections (purpose, usage, how-to-get-ids, aliases, parameters, returns). It front-loads the core purpose and usage. Some redundancy exists (e.g., aliases and keywords overlap), but every section contributes actionable guidance. It could be trimmed slightly, but the structure is effective.

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?

With only one parameter fully documented in the schema and no output schema, the description provides a sample return shape, explains how to obtain valid ids, and gives the exact conditions under which to use the tool. Nothing an agent needs to call it correctly is missing.

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?

The input schema already fully documents the single 'ids' parameter as an array of integers with minItems=1 and a clear description. The tool description adds 'at least one integer required' (redundant) and 'bulk-friendly' (minor). Since schema coverage is 100%, the description adds marginal value, warranting the baseline score of 3.

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 ('Unarchive (restore) one or more previously archived ads') and immediately frames it as the reverse of archive_ad. It also distinguishes from the sibling unarchive_audience by focusing solely on ads, and provides a clear list of user intents that map to this tool.

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?

Explicit 'USE THIS TOOL WHEN' section lists all relevant intents (restore, undelete, recover, reactivate, etc.). It also provides a precise workflow for obtaining archived ad ids via search_ads_by_names with status='archived', and notes that get_ad_details works on archived ids. This is exemplary 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?