ai-content-drop

List generations

list_generations

Read-onlyIdempotent

List the account's recent video generations, newest first, with their status and URLs. 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
`limit`	No	How many to return (1-50). Defaults to 10.

Output Schema

Name	Required	Description	Default
`count`	Yes
`generations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026
- removedOutput schema / properties / generations / items / properties / created_at
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
Changed2 schema fields changedSep 9, 2026
- addedOutput schema / properties / generations / items / properties / image_url
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / generations / items / properties / kind
```
Added value: +{
+  "enum": [
+    "video",
+    "image"
+  ],
+  "type": "string"
+}
```
Changed1 schema field changedSep 1, 2026
- addedInput schema / required
```
Added value: +[]
```
First observedSep 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the description does not need to repeat safety traits. It adds genuinely useful behavioral context: results are newest first, include status and URLs, and require OAuth or an API key header. It does not describe rate limits or pagination beyond the limit parameter, but it covers the most important operational constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loads the core listing behavior and return contents. The second sentence is longer but earns its place by covering the required authentication path in concrete terms. There is essentially no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with one fully documented optional parameter, an output schema, and strong annotations, the description is nearly complete. It adds ordering, returned fields, and auth requirements beyond structured fields. The main remaining gap is explicit routing guidance versus get_generation or other list siblings.

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 description coverage is 100%, and the single optional limit parameter is fully documented in the schema with range and default. The description adds no additional meaning about the limit parameter. Baseline 3 is appropriate when the schema carries all parameter semantics.

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?

The description states a specific verb and resource: list the account's recent video generations. It adds scope and ordering (newest first) and says results include status and URLs. It does not explicitly distinguish this from get_generation or other list tools, but the list-vs-single distinction is reasonably clear from the name and description.

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

Usage Guidelines3/5

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

Usage is implied by 'List the account's recent video generations' and the newest-first ordering. However, the description does not say when to use this instead of get_generation or when-not to use it. The sign-in instructions are useful setup guidance, not tool-selection guidance.

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.