ai-content-drop

Refresh board

refresh_canvas

Read-onlyIdempotent

Re-read a board (same answer as get_canvas). Each read checks rendering generation cards against their jobs: a finished render sets the card's status to done and its media_url. It opens no new view: a board already on screen re-reads itself every 10 seconds while a card renders and for 5 minutes after it last changed, opened or went full screen. Costs no credits. 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
`canvas_id`	Yes	The board id, from list_canvases or create_canvas.

Output Schema

Name	Required	Description	Default
`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

A3.7/5.0

Behavior1/5

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

The annotations declare readOnlyHint=true, but the description says each read sets a generation card's status to done and its media_url, which is a state mutation. That directly contradicts the read-only annotation, even though the description otherwise adds useful auth, cost, and refresh-interval context.

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 core behavior is front-loaded, and the remaining sentences cover materially useful invocation context: render-status side effects, automatic refresh timing, credit cost, and sign-in requirements. There is no filler.

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 not be explained. For a single-parameter read tool, the description supplies the important operational context: render-checking behavior, auto-refresh conditions, cost, and authentication requirements.

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 documents canvas_id as the board id from list_canvases or create_canvas. The description adds no parameter-specific detail beyond that schema, so the baseline 3 is appropriate.

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 uses a specific verb and resource ('Re-read a board') and explicitly relates the result to get_canvas while adding render-status checking behavior. This gives an agent enough to distinguish it from the many board/card siblings 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 gives clear context for use: same answer as get_canvas, no new view opened, auto-refresh behavior while cards render, and no credit cost. However, it stops short of explicitly saying when to choose refresh_canvas versus get_canvas.

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.