ai-content-drop

Get ad job

get_ad_job

Read-onlyIdempotent

Check an ad job: stage and percent while it renders, then the finished video URL, the storyboard sheet, duration, size and the credits charged. Takes the job_id from generate_ad; while the job runs the result carries retry_after_seconds (15). 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
`job_id`	Yes	The job_id returned by generate_ad.

Output Schema

Name	Required	Description
`note`	No	Present only when a succeeded job's charge could not be applied to the account.
`error`	No
`stage`	No	storyboard \| rendering \| done, while known.
`job_id`	Yes
`status`	Yes
`percent`	No
`next_step`	Yes
`video_url`	No	The finished ad with burnt-in captions. Present only when succeeded.
`size_bytes`	No
`studio_url`	No	The job's page in the studio on AI Content Drop.
`credits_used`	Yes	Credits charged for this job when the record reports them; null when a succeeded job's record does not carry the figure (credits_quoted from generate_ad is the ceiling). 0 while running, when failed, or when the charge could not be applied (then note says so).
`duration_seconds`	No
`retry_after_seconds`	No	Present while the job is not terminal.
`storyboard_sheet_url`	No	The storyboard sheet image, when the run produced one.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

removedOutput schema / properties / run_id

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / studio_url

Added value: +{
+  "description": "The job's page in the studio on AI Content Drop.",
+  "type": "string"
+}

AddedSep 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnly/idempotent/non-destructive; the description goes further by disclosing the asynchronous lifecycle (stage and percent while rendering), the concrete 15-second retry hint, and the exact auth path (OAuth prompt or Bearer acd_live_… key with a settings URL). That is materially more than the structured fields carry.

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?

Result contents are front-loaded in the first sentence, then the job_id provenance, then the polling hint, then auth — a sensible priority order. The auth block is long and partly generic boilerplate, but it earns its place for a tool that will fail without it.

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 values need no explanation, yet the description still conveys the intermediate vs. terminal states and the polling cadence an agent needs to drive the loop. Auth, provenance and lifecycle are all covered; nothing required to invoke 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?

Schema coverage is 100% and the schema already says job_id is 'the job_id returned by generate_ad'. The description repeats that same fact and adds no format, prefix or example guidance, so the baseline 3 applies.

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 ('Check an ad job') and immediately enumerates the observable payload: stage, percent, finished video URL, storyboard, duration, size and credits charged. This cleanly positions it as the polling counterpart to generate_ad rather than another generation endpoint.

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?

'Takes the job_id from generate_ad' plus the note that running jobs return retry_after_seconds (15) tells an agent both when to call it and how to loop. It stops short of naming explicit alternatives (e.g. list_generations or get_generation) or saying when not to use it, so it is not a full 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 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.