sprkly

Add media from a URL

sprkly_add_media_from_url

Idempotent

Download an image or video from a public link into sprkly and get a media_id back, for reuse across several posts. You usually do NOT need this: sprkly_schedule_post accepts a link directly in media_urls and pulls it into storage itself whenever the target platform requires that. Reach for this tool only when the user wants one media_id to attach to more than one post. Google Drive and Dropbox share links are converted automatically; the file must be shared publicly. Limit 50 MB. A media_id not used in any post is deleted after 7 days.

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": "sprkly_add_media_from_url"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Direct https link to the image or video file. Must be publicly reachable.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 21, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations: 50 MB size cap, automatic Google Drive/Dropbox share-link conversion, public-sharing requirement, and a 7-day garbage-collection rule for unused media_ids. These are non-obvious operational constraints an agent could not infer from readOnlyHint=false / openWorldHint=true / idempotentHint=true, and nothing contradicts those hints.

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-loads the effect and return value, then the routing advice, then the constraints, in four dense sentences with no filler. Every sentence carries an actionable fact (alternative, conversion, size limit, expiry).

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?

For a single-parameter tool with no output schema, it covers the outcome type (media_id), accepted URL sources, size limit, and lifecycle of the returned id. Nothing an agent needs to call it correctly or to decide against calling it is missing.

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 is 3; the description still adds value by clarifying that Drive/Dropbox share links (not just direct file URLs) are accepted and converted, which softens the schema's 'direct https link' wording. It also documents the return value (media_id) despite there being no output schema, though it gives no format details for the URL argument itself.

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 ('Download an image or video from a public link into sprkly') plus the concrete outcome ('get a media_id back'). It is immediately distinguishable from the two nearest siblings, sprkly_schedule_post (which pulls links itself) and sprkly_upload_media (presumably local files).

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?

Explicitly discourages use ('You usually do NOT need this'), names the preferred alternative (sprkly_schedule_post with media_urls), and gives the precise condition that selects this tool: when one media_id must be attached to more than one post. When-not and when-to-use are both present.

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

All sprkly 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.

Resources

Need Help?