SendIt

Create Upload Session

create_upload_session

Create a browser upload link for media files. ALWAYS use this when the user shares an image or video in chat — their file is local and cannot be passed directly to publish_content.

WORKFLOW:

Call this tool to get an uploadUrl
Give the user the link to open in their browser and upload their file
After upload, call get_upload_session to get the public media URL(s)
Use the returned URL with publish_content or schedule_content

Supports up to 20 files per session. Expires in 15 minutes.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mediaType`	No	Optional hint for expected media type

Output Schema

TableJSON Schema

Name	Required	Description	Default
`files`	No
`status`	No
`isError`	No
`success`	No
`mediaUrl`	No
`expiresAt`	No
`mediaType`	No
`mediaUrls`	No
`sessionId`	No
`uploadUrl`	No
`mediaItems`	No
`errorMessage`	No
`followUpSuggestions`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedMay 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "errorMessage": {
+      "type": "string"
+    },
+    "expiresAt": {
+      "type": "string"
+    },
+    "files": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "followUpSuggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "isError": {
+      "type": "boolean"
+    },
+    "mediaItems": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "mediaType": {
+      "type": "string"
+    },
+    "mediaUrl": {
+      "type": "string"
+    },
+    "mediaUrls": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "sessionId": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "uploadUrl": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With all annotations false, the description carries the full burden. It discloses key behavioral traits: creates a browser link, user must open it to upload, supports up to 20 files, expires in 15 minutes, and the file is local. This goes well beyond the minimal annotation info and sets clear expectations.

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?

The description is well-structured with a clear opening, a numbered workflow, and key constraints (file limit, expiration). Every line adds value; the workflow steps are necessary and concise, making it easy to follow without unnecessary fluff.

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?

Despite having only one optional parameter and an output schema, the description is self-sufficient: it covers the tool's purpose, exact usage scenario, step-by-step workflow, and operational limits. There's no missing information an agent would need to invoke it correctly.

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?

The input schema has 100% coverage for the single optional parameter mediaType, including an enum and description. The description doesn't add new parameter-level semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource: 'Create a browser upload link for media files.' It clearly distinguishes itself from siblings like upload_media and get_upload_session by focusing on generating a user-facing upload URL, and it explicitly mentions the context of chat-shared images/videos.

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?

Provides explicit when-to-use guidance: 'ALWAYS use this when the user shares an image or video in chat.' It also explains why (local file cannot be passed directly to publish_content), and maps out a full workflow including next steps (get_upload_session, publish_content/schedule_content), effectively differentiating from alternatives.

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

All SendIt tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3/5.0

Disambiguation2/5

With 148 tools, there is significant overlap. For example, generate_content, publish_ai, generate_post_bundle, and request_project_content all generate content; get_analytics, get_unified_analytics, get_post_analytics, get_ad_performance, and get_unified_ad_report all fetch performance metrics; and list_inbox vs list_conversations blur comment and conversation management. Descriptions help, but boundaries between tools are often unclear.

Naming Consistency3/5

Most tools follow a verb_noun pattern (e.g., list_teams, create_goal, delete_post), but there are notable deviations: create_library_item vs save_to_library, publish_content vs publish_ai, schedule_content vs schedule_content_advanced, and connect_platform vs connect_connector. Mixed prefixes like 'autopilot_', 'check_', and 'get_' are fine, but overlapping verbs and a hyphen in 'connect_linkedin-page' reduce consistency.

Tool Count1/5

148 tools is extreme for any server. Even for a broad social media management platform, this is far beyond what an agent can effectively navigate. The count is unwieldy and suggests the surface should be split into multiple focused servers (publishing, analytics, connectors, workflows, etc.).

Completeness3/5

The core social publishing workflow is well covered (create, schedule, publish, edit, delete, retry), and there are extensive features for analytics, workflows, connectors, and AI agents. However, some resources have CRUD gaps: no update/delete for brand voices, no delete_project, no update/delete for Product Hunt goals, and no explicit get_workflow. These are workable but notable omissions.

Resources

Need Help?