Skip to main content
Glama
Sign In

AutomateSocials

by net.automatesocials
OverviewDiscussionsAdmin

Import media

upload_media_from_url

Downloads a publicly reachable file into storage and returns a stable URL to use in posts. Use this for images or video that already live on the web.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublicly reachable URL of the file.
altTextNoWhat the picture shows, for people who cannot see it; at most 1000 characters. Sent with the picture to LinkedIn, X, Facebook and Instagram (not with a video).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / altText / description
      Previous value: -"Accessibility description."New value: +"What the picture shows, for people who cannot see it; at most 1000 characters. Sent with the picture to LinkedIn, X, Facebook and Instagram (not with a video)."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Adds real context beyond the annotations: the source must be publicly reachable and the result is a stored file with a stable URL. However, annotations declare idempotentHint=false and the description never warns that re-importing the same URL creates a new media object, nor does it say what happens when the URL is unreachable or which formats/sizes are rejected.

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?

Two short sentences, zero filler, with the core action and its constraint front-loaded before the usage hint.

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?

For a two-parameter import tool with no output schema, the description covers what is fetched, where it goes, and what is returned. The remaining gap is failure/duplicate behavior on an openWorld, non-idempotent write.

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 both url and altText are already documented, including the 1000-character limit and which platforms receive altText. The description only reinforces the 'publicly reachable' constraint for url and says nothing about altText, so the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('downloads a publicly reachable file into storage') plus the concrete outcome ('returns a stable URL to use in posts'). It implicitly separates itself from create_presigned_upload_url/generate_image by scoping to files that already live on the web, but it doesn't name those siblings explicitly.

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?

'Use this for images or video that already live on the web' gives a usage condition, but there is no explicit exclusion pointing to create_presigned_upload_url, complete_upload, generate_image, or add_knowledge_from_url for the adjacent cases.

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

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