Skip to main content
Glama

evidence_upload_link

Issues presigned URLs (1 h, the same expiry as every other MCP upload link) to PUT screenshots or PDFs that will serve as evidence in the dispute of an order you bought; it returns each one's storageRef, which is what submit_evidence asks for. With count it issues several at once, all of the same type (an evidence file usually carries several screenshots); the answer says how many it issued and when they expire. It asks for the orderId and only issues them to that order's buyer. JPEG, PNG or PDF only, up to 10 MB each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesFile type: image/jpeg, image/png or application/pdf. Nothing else.
countNoHow many links to issue at once, all of the same `type` (1-5; 1 by default). A case file usually carries several screenshots: asking for them in one call saves round trips. To mix types, one call per type.
orderIdYesId of the disputed order whose case file you are going to add to (the orderId or the purchaseId from my_purchases). Only the buyer of that order can file evidence.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
linksYesOne link per file, all of the same `mimeType`. It may bring back fewer than requested if the upload quota runs out halfway.
issuedYesHow many links were actually issued.
maxBytesYesMaximum size in bytes of each file (this is not money: it is a count).
mimeTypeYesFile type these links accept.
expiresAtYesWhen the links expire, in ISO 8601.
expiresInYesHow long they last, said in words.
storageRefYesThe `storageRef` of the first link, repeated on its own.
instructionsYesWhat to do with the links, step by step.
presignedUrlYesThe first one in `links`, repeated on its own for older clients.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / allOf
      Removed value: -[
      -  {
      -    "anyOf": [
      -      {
      -        "required": [
      -          "orderId"
      -        ]
      -      },
      -      {
      -        "required": [
      -          "ordenId"
      -        ]
      -      }
      -    ]
      -  },
      -  {
      -    "anyOf": [
      -      {
      -        "required": [
      -          "type"
      -        ]
      -      },
      -      {
      -        "required": [
      -          "tipo"
      -        ]
      -      }
      -    ]
      -  }
      -]
    • changedInput schema / properties / count / description
      Previous value: -"How many links to issue at once, all of the same `tipo` (1-5; 1 by default). A case file usually carries several screenshots: asking for them in one call saves round trips. To mix types, one call per type."New value: +"How many links to issue at once, all of the same `type` (1-5; 1 by default). A case file usually carries several screenshots: asking for them in one call saves round trips. To mix types, one call per type."
    • removedInput schema / properties / ordenId
      Removed value: -{
      -  "deprecated": true,
      -  "description": "DEPRECATED alias of `orderId`: it still works, but use `orderId` (it will be removed in a future round, no date yet). Id of the disputed order whose case file you are going to add to (the ordenId or the compraId from my_purchases). Only the buyer of that order can file evidence.",
      -  "type": "string"
      -}
    • changedInput schema / properties / orderId / description
      Previous value: -"Id of the disputed order whose case file you are going to add to (the ordenId or the compraId from my_purchases). Only the buyer of that order can file evidence."New value: +"Id of the disputed order whose case file you are going to add to (the orderId or the purchaseId from my_purchases). Only the buyer of that order can file evidence."
    • removedInput schema / properties / tipo
      Removed value: -{
      -  "deprecated": true,
      -  "description": "DEPRECATED alias of `type`: it still works, but use `type` (it will be removed in a future round, no date yet). File type: image/jpeg, image/png or application/pdf. Nothing else.",
      -  "type": "string"
      -}
    • addedInput schema / required
      Added value: +[
      +  "orderId",
      +  "type"
      +]
    • removedInput schema / x-bernuvia-aliases
      Removed value: -{
      -  "orderId": "ordenId",
      -  "type": "tipo"
      -}
  2. Changed16 schema fields changed
    • changedInput schema / properties / count / description
      Previous value: -"Cuántos enlaces emitir de golpe, todos de ese mismo `tipo` (1-5; por defecto 1). Un expediente suele llevar varias capturas: pedirlas en una llamada ahorra viajes. Para mezclar tipos, una llamada por tipo. / How many links to issue at once, all of the same type."New value: +"How many links to issue at once, all of the same `tipo` (1-5; 1 by default). A case file usually carries several screenshots: asking for them in one call saves round trips. To mix types, one call per type."
    • changedInput schema / properties / ordenId / description
      Previous value: -"ALIAS RETIRADO de `orderId`: sigue funcionando, pero usa `orderId` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `orderId`. Id de la orden en disputa a cuyo expediente vas a aportar (el ordenId o el compraId de my_purchases). Solo el comprador de esa orden puede aportar pruebas."New value: +"DEPRECATED alias of `orderId`: it still works, but use `orderId` (it will be removed in a future round, no date yet). Id of the disputed order whose case file you are going to add to (the ordenId or the compraId from my_purchases). Only the buyer of that order can file evidence."
    • changedInput schema / properties / orderId / description
      Previous value: -"Id de la orden en disputa a cuyo expediente vas a aportar (el ordenId o el compraId de my_purchases). Solo el comprador de esa orden puede aportar pruebas."New value: +"Id of the disputed order whose case file you are going to add to (the ordenId or the compraId from my_purchases). Only the buyer of that order can file evidence."
    • changedInput schema / properties / tipo / description
      Previous value: -"ALIAS RETIRADO de `type`: sigue funcionando, pero usa `type` (se quitará en una tanda futura, aún sin fecha). / DEPRECATED alias of `type`. Tipo del archivo: image/jpeg, image/png o application/pdf. Nada más."New value: +"DEPRECATED alias of `type`: it still works, but use `type` (it will be removed in a future round, no date yet). File type: image/jpeg, image/png or application/pdf. Nothing else."
    • changedInput schema / properties / type / description
      Previous value: -"Tipo del archivo: image/jpeg, image/png o application/pdf. Nada más."New value: +"File type: image/jpeg, image/png or application/pdf. Nothing else."
    • changedOutput schema / properties / expiresAt / description
      Previous value: -"Cuándo caducan los enlaces, en ISO 8601."New value: +"When the links expire, in ISO 8601."
    • changedOutput schema / properties / expiresIn / description
      Previous value: -"Lo que duran, dicho en palabras."New value: +"How long they last, said in words."
    • changedOutput schema / properties / instructions / description
      Previous value: -"Qué hacer con los enlaces, paso a paso."New value: +"What to do with the links, step by step."
    • changedOutput schema / properties / issued / description
      Previous value: -"Cuántos enlaces se emitieron de verdad."New value: +"How many links were actually issued."
    • changedOutput schema / properties / links / description
      Previous value: -"Un enlace por archivo, todos del mismo `mimeType`. Puede traer menos de los pedidos si el cupo de subidas se agota a mitad."New value: +"One link per file, all of the same `mimeType`. It may bring back fewer than requested if the upload quota runs out halfway."
    • changedOutput schema / properties / links / items / properties / presignedUrl / description
      Previous value: -"URL firmada a la que se sube el archivo con un PUT."New value: +"Signed URL the file is uploaded to with a PUT."
    • changedOutput schema / properties / links / items / properties / storageRef / description
      Previous value: -"Referencia del archivo en el almacén; es lo que pide submit_evidence."New value: +"Reference of the file in the store; it is what submit_evidence asks for."
    • changedOutput schema / properties / maxBytes / description
      Previous value: -"Tamaño máximo en bytes de cada archivo (no es dinero: es una cuenta)."New value: +"Maximum size in bytes of each file (this is not money: it is a count)."
    • changedOutput schema / properties / mimeType / description
      Previous value: -"Tipo del archivo que aceptan estos enlaces."New value: +"File type these links accept."
    • changedOutput schema / properties / presignedUrl / description
      Previous value: -"El primero de `links`, repetido suelto para los clientes antiguos."New value: +"The first one in `links`, repeated on its own for older clients."
    • changedOutput schema / properties / storageRef / description
      Previous value: -"El `storageRef` del primer enlace, repetido suelto."New value: +"The `storageRef` of the first link, repeated on its own."
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: 1h expiry, buyer-only authorization requirement, accepted MIME types, 10 MB size cap, and count range 1-5. It also discloses the returned storageRef and how it relates to submit_evidence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Information-dense and front-loaded with the core action, but the sentences are long and somewhat run-on, packing expiry, return value, auth, and constraints into one flowing block.

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?

Complete for an upload-link tool: it covers authorization, file constraints, expiry, count behavior, and the return value's role, even though an output schema exists. Nothing critical is missing for correct invocation.

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 schema already documents type, count, and orderId in detail. The description restates most of this (buyer-only, same type for all, count) without adding substantial new syntax or format meaning beyond the schema. Baseline 3 for high coverage.

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 (issues presigned URLs to PUT evidence files for an order dispute), and disambiguates from siblings like image_upload_link and zip_upload_link by tying it to dispute evidence. It also names the downstream consumer (submit_evidence) via the returned storageRef.

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?

Clear context: it's for adding evidence to a dispute of an order you bought, and count is for issuing several of one type. It states the buyer-only restriction. It doesn't explicitly say 'use image_upload_link for non-evidence images', but the evidence framing makes the routing implicit.

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