SendIt

Get Upload Session

get_upload_session

Read-onlyIdempotent

Check the status of an upload session and get the media URL(s) once uploaded.

Call this after the user clicks the upload link to see if they've completed the upload.

Returns: • status: 'pending' - User hasn't uploaded yet • status: 'uploaded' - Upload complete, includes mediaUrl, mediaUrls, fileCount, mediaItems • status: 'expired' - Session expired (15 min limit)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sessionId`	Yes	The session ID returned from create_upload_session

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.5/5.0

Behavior5/5

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

The annotations already declare readOnlyHint=true and idempotentHint=true, so the read-only behavior is known. The description adds valuable behavioral context by detailing the three possible statuses (pending, uploaded, expired) and the 15-minute session expiry limit. This goes beyond what annotations provide and helps the agent understand polling behavior and expected return states.

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 compact and well-structured. It opens with a one-sentence purpose, follows with a single usage instruction, and then uses a concise bullet list for return states. Every sentence adds value, and there is no redundancy or 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?

For a simple one-parameter polling tool with an output schema (which likely details the return structure), the description provides sufficient context: it explains the main status states, the expiry limit, and when to call it. The combination of the description, annotations, and schema fully equips the agent to use the tool 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% description coverage: the single parameter 'sessionId' is described as 'The session ID returned from create_upload_session.' The description does not add any semantic meaning beyond the schema, so the baseline score of 3 is appropriate because the schema carries the full burden.

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 uses a specific verb and resource: 'Check the status of an upload session and get the media URL(s) once uploaded.' This clearly defines the tool's function and distinguishes it from sibling tools like create_upload_session, which creates the session, and check_ai_media_status, which likely handles AI media statuses. The purpose is unambiguous and specific.

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 provides explicit timing guidance: 'Call this after the user clicks the upload link to see if they've completed the upload.' This clearly indicates when to use the tool and implies the preceding creation step. However, it does not explicitly name alternatives or explain when not to use it, so it falls just short of a perfect score.

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?