Skip to main content
Glama

Finish a large-file upload (step 3 of 3)

finish_upload

Publish the file you just sent with curl after prepare_upload. Pass the ticket prepare_upload gave you. Returns the private link (the SAME link if you passed page to prepare_upload). If it says the file wasn't found, the curl step did not succeed or took too long — run prepare_upload again for a fresh ticket and re-send.

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": {
      "ticket": "<ticket>"
    },
    "name": "finish_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoOptional title for a NEW page. A replaced page keeps its existing title.
expiryNoOptional expiry for a new page. Default 'never' (Free tier falls back to 7 days unless an always-on slot is free).
ticketYesThe ticket from prepare_upload, exactly as given.
projectNoOptional project (folder) BY NAME for a new page; created if it doesn't exist.
passwordNoOptional viewer password for a new page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it delivers key behavior: the return value (private link), the identity guarantee (same link when a page was replaced), and the failure mode plus remedy. It does not mention auth requirements, whether repeating the call with the same ticket is idempotent, or how long the ticket stays valid before the 'took too long' condition triggers.

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 action and the required ticket, followed by the return value and then the error branch. Every sentence carries operational information and none restates the title.

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 5-parameter tool with no output schema, the description covers the critical unknowns: what is returned and what to do when it fails. Minor gaps remain around authorization or tier limits on the returned link, but nothing that would cause an agent to invoke it incorrectly.

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 all five parameters including ticket, title, expiry, project, and password are already documented. The description only reiterates the ticket handoff and the page-replacement link identity, adding no new meaning about the remaining parameters, 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 ('Publish the file you just sent with curl') and anchors it in the workflow as the step after prepare_upload. An agent can distinguish this from prepare_upload and from create_page without opening any 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 to call this after the curl upload following prepare_upload, and gives a concrete recovery path when the ticket is stale ('run prepare_upload again for a fresh ticket and re-send'). Both the happy path and the failure path name the correct sibling tool.

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