Skip to main content
Glama

ai-content-drop

by com.aicontentdrop
OverviewDiscussionsAdmin

Get saved ad

get_saved_ad
Read-onlyIdempotent

Read one saved competitor ad in full, with its stored decode (the ad's formula and a recreation prompt) when it has one. Costs no credits; never runs a decode. SIGN-IN REQUIRED: connect this server with OAuth (the host prompts for it), or add an API key header "Authorization: Bearer acd_live_…" created at https://aicontentdrop.com/settings/integrations.

Input Schema

NameRequiredDescriptionDefault
ad_idYesA saved ad's id, from list_saved_ads or save_competitor_ad.

Output Schema

NameRequiredDescriptionDefault
adYes
decodeYesThe ad's formula, layer by layer, plus a generation-ready prompt.
next_stepYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / ad / properties / demo / description
      Previous value: -"True for a sample row: not a real ad. Never present a sample as live data."New value: +"True for a sample row: not a real ad and not live data."
  2. Changed4 schema fields changed
    • removedOutput schema / properties / ad / properties / saved_at
      Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • changedOutput schema / properties / ad / required
      Previous value: -[
-  "id",
-  "ad_ref",
-  "platform",
-  "advertiser_name",
-  "ad_copy",
-  "media_url",
-  "media_type",
-  "estimated_spend",
-  "engagement_score",
-  "running_days",
-  "hook_text",
-  "cta_text",
-  "ad_url",
-  "demo",
-  "decoded",
-  "saved_at"
-]New value: +[
+  "id",
+  "ad_ref",
+  "platform",
+  "advertiser_name",
+  "ad_copy",
+  "media_url",
+  "media_type",
+  "estimated_spend",
+  "engagement_score",
+  "running_days",
+  "hook_text",
+  "cta_text",
+  "ad_url",
+  "demo",
+  "decoded"
+]
    • removedOutput schema / properties / decode / properties / decodedAt
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / decode / required
      Previous value: -[
-  "layers",
-  "recreationPrompt",
-  "confidence",
-  "decodedAt"
-]New value: +[
+  "layers",
+  "recreationPrompt",
+  "confidence"
+]
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new operational facts: zero credit cost, no decode execution, and the full auth path (OAuth via host prompt, or Bearer acd_live_… API key header with a creation URL). That is the kind of pre-call context an agent needs and cannot get from the schema.

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 purpose sentence, then the cost/behavior clause, then auth — a logical order with no filler. The auth sentence is long but carries required setup detail, so it 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?

An output schema exists, so return structure needn't be described. With cost, decode behavior, auth requirements, and id provenance all covered, an agent has everything needed to call this correctly.

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 100% and the single ad_id parameter is fully documented with provenance ('from list_saved_ads or save_competitor_ad'). The description adds no further meaning about the parameter, so this is the baseline case where the schema does all the work.

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?

States a specific verb and resource ('Read one saved competitor ad in full') plus the notable payload ('stored decode — the ad's formula and a recreation prompt'). This clearly separates it from list_saved_ads (listing), save_competitor_ad (writing), and decode_ad (running a new decode).

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

Usage Guidelines4/5

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

Explicitly frames the cost/behavior contrast — 'Costs no credits; never runs a decode' — which implicitly routes agents to decode_ad when they need a fresh decode, and the schema points to list_saved_ads/save_competitor_ad for the ad_id. It lacks an explicit 'use this instead of X when Y' sentence, keeping it just under a 5.

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

All ai-content-drop 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