AutomateSocials

Prepare upload

create_presigned_upload_url

Returns a presigned URL for uploading a local file directly to storage. PUT the file bytes to uploadUrl with the same Content-Type, call complete_upload with the mediaId, then use mediaId or publicUrl when creating a post.

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": {
      "filename": "<filename>",
      "contentType": "<contentType>"
    },
    "name": "create_presigned_upload_url"
  }
}

Input Schema

Name	Required	Description
`altText`	No	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).
`filename`	Yes	Original file name, used for the extension.
`contentType`	Yes	MIME type, for example image/jpeg or video/mp4.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / altText

Added value: +{
+  "description": "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).",
+  "type": "string"
+}

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only declare the safety profile (not read-only, open-world, not idempotent, non-destructive); the description adds the important behavioral fact that the URL is a transient intermediate and that the upload is not finished until complete_upload is called. It omits URL expiry and any size/type limits, which are the remaining unknowns for a presigned-upload flow.

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 sentences, front-loaded with what the tool returns, followed by the exact call sequence. Every clause carries operational information and nothing is wasted.

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?

There is no output schema, and the description compensates by naming the returned fields (uploadUrl, mediaId, publicUrl) and where each is consumed downstream. Missing only the operational limits an agent would want: URL lifetime and any file-size or type constraints.

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 the baseline is 3, but the description adds real meaning by tying contentType to the subsequent PUT ("with the same Content-Type"), which explains why the MIME type must be supplied here rather than at upload time. altText and filename are left entirely to the schema.

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?

"Returns a presigned URL for uploading a local file directly to storage" states a specific verb and resource, and the qualifier "local file" implicitly separates it from upload_media_from_url. It never names that sibling, so the differentiation is inferential rather than explicit.

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?

The description gives a clear end-to-end sequence: PUT the bytes to uploadUrl, call complete_upload with the mediaId, then use mediaId or publicUrl in create_post. That is strong contextual guidance, but it never states when NOT to use this tool (e.g. when the file already lives at a URL, where upload_media_from_url applies).

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

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