ai-content-drop

Update card

update_card

Destructive

Change a card: merge fields into its data (text or title on a text card; prompt, model, kind, aspect_ratio, duration, resolution or image_url on a generation card; title or caption on a media card; label on a frame), or move and resize it. Costs no credits. status, job_id, job_kind, quote_id, media_url, thumbnail_url, credits_used and error are set by the server when a card runs and are refused here. A per-second model is priced from the card's duration and resolution, and run_generation_card checks its quote against them. 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
`data`	No	Fields to merge into the card's data; fields not named are kept.
`width`	No	Optional card width in pixels.
`height`	No	Optional card height in pixels.
`card_id`	Yes	The card id, from cards[] on the board.
`position`	No	Optional { x, y } in board pixels. When omitted the server places the card in the first free grid cell.
`revision`	No	The board revision this change is based on (from the last board you saw). Optional: when omitted the tool reads the current one first.
`canvas_id`	Yes	The board id, from list_canvases or create_canvas.

Output Schema

Name	Required	Description	Default
`card`	Yes
`canvas`	Yes
`next_step`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

removedOutput schema / properties / canvas / properties / updated_at

Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}

changedOutput schema / properties / canvas / required

Previous value: -[
-  "id",
-  "name",
-  "revision",
-  "card_count",
-  "updated_at",
-  "link",
-  "cards",
-  "edges"
-]New value: +[
+  "id",
+  "name",
+  "revision",
+  "card_count",
+  "link",
+  "cards",
+  "edges"
+]

Changed2 schema fields changedSep 23, 2026

addedOutput schema / properties / canvas / properties / edges / items / description

Added value: +"A connection drawn from one card to the next: { id, source, target, label? }. data.role start_image means the source card's finished image is the target card's start frame."

addedOutput schema / properties / canvas / properties / edges / items / properties

Added value: +{
+  "id": {
+    "type": "string"
+  },
+  "label": {
+    "description": "Text drawn on the line, when it has one."
+  },
+  "source": {
+    "description": "The card the connection starts from.",
+    "type": "string"
+  },
+  "target": {
+    "description": "The card it leads to.",
+    "type": "string"
+  }
+}

AddedSep 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations it adds real behavioral context: no credit cost, merge semantics (unnamed fields kept), server-side refusal of run-managed fields, and explicit auth requirements (OAuth or Bearer API key with signup URL). It does not explain what a destructiveHint=true overwrite of an existing data field means in practice, which is the one behavioral gap.

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 core action and field mapping are front-loaded, and every sentence is information-dense with no filler. The per-second-model pricing/quote sentence is tangential to this tool and slightly bloats an otherwise tight definition.

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 7-parameter mutation tool with a full output schema and annotations, this covers field semantics, merge behavior, refused fields, and auth — everything needed to invoke it correctly. Minor gaps: no note on revision-conflict handling or the practical meaning of the destructive overwrite.

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?

Schema coverage is 100%, so baseline would be 3, but the description goes further by unpacking the opaque generic 'data' object into per-card-type field sets — meaning the schema cannot convey. Width/height/position/revision semantics remain carried by the schema, which is acceptable.

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 gives a specific verb ('Change a card') and then enumerates exactly which fields are mutably per card type (text/title on text cards; prompt/model/kind/aspect_ratio/duration/resolution/image_url on generation cards; etc.), plus move/resize. This is far more specific than the sibling add_* / move_cards tools and lets an agent distinguish it without opening the schema.

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?

It clearly establishes the context in which to call it (editing card data or geometry) and states exclusions — server-managed fields like status, job_id, media_url are refused here. It does not explicitly name alternatives such as move_cards or arrange_cards for repositioning, so routing between overlapping siblings is left partly to inference.

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.