Skip to main content
Glama

ai-content-drop

by com.aicontentdrop
OverviewDiscussionsAdmin

Create board

create_canvas

Create a new, empty board and return it. Costs no credits. Cards are added to it with the add_* tools. 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

NameRequiredDescriptionDefault
nameNoBoard name, up to 100 characters. Defaults to Untitled Canvas.

Output Schema

NameRequiredDescriptionDefault
canvasYes
next_stepYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+]
  2. Changed2 schema fields changed
    • 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"
+  }
+}
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds genuinely new facts: the operation costs no credits and the board starts empty. The SIGN-IN REQUIRED block spells out both OAuth and API-key auth with a concrete header format and URL, which is real operational context. It does not address limits such as duplicate names or a per-account board cap.

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 the action and cost, followed by the follow-on hint and then auth. The auth sentence is long but every clause is actionable (mechanism, header name, URL), so it earns its space; the only mild redundancy is restating the credential prefix format.

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?

With an output schema present, the description needn't describe the returned board, and it correctly focuses on cost, auth, and next steps instead. Visibility/sharing semantics of a newly created board are the one gap an agent might still wonder about.

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?

Only one optional parameter and the schema already documents it fully, including the 100-character limit and the 'Untitled Canvas' default. The description adds nothing about the name argument, so the baseline of 3 applies when the schema carries the load.

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 plus the key qualifier 'new, empty board and return it', which separates it cleanly from list_canvases, get_canvas, and rename_canvas. An agent can identify the operation 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?

Gives clear situational context by naming the follow-on path ('Cards are added to it with the add_* tools'), which tells the agent this is the setup step before add_frame/add_text_card etc. It stops short of explicit when-not guidance or pointing at list_canvases/get_canvas for existing boards.

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 toolsInspect
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.

Resources