ai-content-drop

List saved ads

list_saved_ads

Read-onlyIdempotent

List the competitor ads saved on the account, newest first: id, advertiser, hook, media and whether a decode is stored. Costs no credits. Its ids are the ad_id that get_saved_ad, decode_ad and ad_to_canvas_card take. 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

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ads`	Yes
`count`	Yes
`next_step`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / ads / items / 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."

Changed2 schema fields changedOct 8, 2026

removedOutput schema / properties / ads / items / properties / saved_at
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```

changedOutput schema / properties / ads / items / 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"
+]

AddedSep 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds value beyond them: zero credit cost, deterministic newest-first ordering, the fields returned, and the required OAuth or Bearer API-key authentication with a concrete header format.

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 purpose, then return fields, cost, id linkage, and auth — a sensible priority order with no filler sentences. The sign-in block is verbose but operationally necessary, so the density is justified.

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?

Zero parameters, an output schema for return values, and annotations for safety — the description fills the remaining gaps (auth, cost, ordering, id reuse). Nothing an agent needs in order to call this correctly is missing.

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?

The tool takes no parameters, so the baseline is 4. The description goes slightly further by describing the fields of each item and their ordering, but return shape is already covered by the output schema, so no additional credit is warranted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb + resource ('List the competitor ads saved on the account') plus ordering ('newest first') and the returned field set. It is clearly distinct from search_competitor_ads because it is scoped to ads already saved, though it never names that sibling explicitly to make the contrast airtight.

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?

Provides forward routing: the returned ids are exactly the ad_id consumed by get_saved_ad, decode_ad and ad_to_canvas_card, so an agent knows this is the lookup step preceding those tools. It also notes 'Costs no credits', a useful decision input. It stops short of saying when to prefer this over search_competitor_ads.

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 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.