Skip to main content
Glama

Get Upload Ticket

get_upload_ticket
Idempotent

Called by the upload box that open_upload_widget shows, once per file, to authorize storing that file in AdaptlyPost media storage. Returns a ticket valid for 5 minutes. Do not call this yourself; call open_upload_widget instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_upload_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with expiresAt and uploadUrl for the upload box.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / result / properties / expiresAt / description
      Added value: +"ISO 8601 time the ticket stops working, 5 minutes after it was issued"
    • addedOutput schema / properties / result / properties / uploadUrl / description
      Added value: +"Address the upload box sends the file to, together with the ticket"
  2. Changed5 schema fields changed
    • addedOutput schema / properties / result / additionalProperties
      Added value: +false
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "expiresAt": {
      +    "type": "string"
      +  },
      +  "uploadUrl": {
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "expiresAt",
      +  "uploadUrl"
      +]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds real context beyond them: the caller identity, one-ticket-per-file cadence, and a 5-minute validity window. It does not say what happens when a ticket expires or whether a ticket is single-use, so it stops short of full behavioral disclosure.

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?

Three short sentences, front-loaded with the primary purpose, followed by return behavior and then the routing warning. No redundant restatement of the title or schema.

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?

An output schema exists, so return shape needs no explanation, and the description correctly focuses on caller, cadence, and TTL. Remaining gaps — expiry/error behavior and whether a ticket can be reused — are minor for a single optional-parameter widget-callback tool.

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% and the workspaceId documentation is already thorough (source from list_workspaces, omission semantics, cross-workspace consistency). The description adds no further meaning about the parameter, so the baseline 3 applies.

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 — authorizes storing a file in AdaptlyPost media storage and returns a short-lived ticket — plus the exact caller (the upload box shown by open_upload_widget) and cadence (once per file). This is enough to distinguish it from open_upload_widget and from upload_media without opening either schema.

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 says 'Do not call this yourself; call open_upload_widget instead,' naming the alternative and the condition that selects it. It also tells the agent the call originates from the widget, so there is no ambiguity about direct invocation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources