Skip to main content
Glama
Sign In

Socialync

by io.github.JackVitick
OverviewDiscussionsAdmin

import-claude-motion-from-url

Import a video made with Claude Motion into the user's Socialync media library so it can be posted. Use this when the user wants to post, schedule or send a Claude Motion video to Socialync. Call it promptly with the download URL Claude Motion provides (it expires within minutes). Returns a mediaId to pass to publish_scheduled or schedule_post_draft (video posts work on every platform, YouTube also needs a title). Importing does not publish anything. Schedule the video within 12 hours of importing: media that no post uses is cleaned up after that.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "import-claude-motion-from-url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe Claude Motion MP4 download URL (https://*.claudeusercontent.com). Pass it exactly as given.
titleNoA name for the video in the media library, e.g. "Product launch teaser".
download_tokenNoAccess token for the URL when Claude Motion gives one separately. Sent only to the Claude Motion host.
claude_design_project_idNoThe originating Claude Motion project id, if provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say it is a non-destructive, open-world write; the description goes well beyond that by disclosing URL expiry (minutes), the returned mediaId contract, and that unused media is garbage-collected after 12 hours. These are operational facts the agent cannot get from annotations and that change how urgently it must act.

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?

Front-loaded with purpose, then trigger, then the call-promptly urgency, then the return value and lifecycle constraint. Every sentence carries distinct operational information; nothing is repeated from the title or schema.

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 no output schema, the description supplies the return value (mediaId) and where to pass it, plus the cleanup deadline an agent needs to sequence a follow-up schedule call. For a 4-param import tool it covers everything needed to call it correctly.

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; the description still adds meaning by flagging that the URL must be passed exactly as given because it expires, and that a title is required for YouTube even though it is optional in the schema. It does not explain download_token or claude_design_project_id, but those are already well documented.

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 (Import) and resource (a Claude Motion video) plus the destination (the user's Socialync media library) and the immediate downstream consumer (a mediaId). Names sibling tools (publish_scheduled, schedule_post_draft) and contrasts with the sibling create_media_upload by tying the source to Claude Motion, so an agent can route correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit trigger ('Use this when the user wants to post, schedule or send a Claude Motion video to Socialync') and an explicit non-effect ('Importing does not publish anything') that steers the agent away from publish_now/publish_scheduled for the publish step. The 12-hour scheduling window is given as an actionable constraint rather than left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Socialync 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