ai-content-drop

Add text card

add_text_card

Add a text card (a note, an idea, a script line) to a board. The server places it on a grid unless a position is given. Costs no credits. Returns the whole board and the new card. 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
`text`	Yes	The card's text, up to 4000 characters.
`color`	No	Optional colour name or hex the website uses for the card.
`title`	No	Optional title, up to 200 characters.
`width`	No	Optional card width in pixels.
`height`	No	Optional card height in pixels.
`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.2/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses auto-placement on the grid when position is omitted, that the operation consumes no credits, that the whole board plus the new card are returned, and the full auth requirement (OAuth host prompt or Bearer acd_live_… API key with the settings URL). These are exactly the preconditions an agent needs that readOnlyHint=false/destructiveHint=false do not convey.

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 behaviour, then auth, and every sentence is informative. The auth sentence is long (two mechanisms plus a URL) but it is genuinely required information rather than padding.

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?

With an output schema present the description needn't explain return shape, yet it still summarises it; combined with credit cost, placement defaults, and auth it covers everything needed to invoke an 8-parameter mutation tool 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 description coverage is 100%, so the schema already documents all eight parameters including limits (4000 chars, 200-char title) and the revision fallback. The description only restates the position-vs-grid behaviour, adding no new semantics, 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 ('Add a text card') and disambiguates the content type with 'a note, an idea, a script line', which separates it from sibling card-creators (add_media_card, add_generation_card, add_frame). The board-bound scope is explicit, so an agent can pick 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 Guidelines3/5

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

Usage is implied by the examples of what a text card is and by 'Costs no credits', which helps an agent prefer it over credit-consuming generation tools. However, it never states when-not to use it or names an alternative sibling explicitly (e.g. 'for images use add_media_card').

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.