Skip to main content
Glama

get_pdf_upload_url

Get a presigned URL to upload a PDF that a DM automation will hand out.

Use this to attach a downloadable PDF (a recipe, a guide, a price list) to an automation: PUT the raw PDF bytes to upload_url as a plain HTTP PUT with Content-Type: application/pdf — do NOT route the bytes through this MCP connection. Once the PUT succeeds, pass public_url as the url of a dm_buttons entry with kind="pdf" in create_automation / update_automation.

filename is only for your own reference; the stored object is always a .pdf under a durable prefix, so the link keeps working long-term. upload_url expires in expires_in seconds.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "get_pdf_upload_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameNoattachment.pdf
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
expires_inYes
public_urlYes
upload_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: upload raw PDF bytes directly to upload_url with a plain HTTP PUT and Content-Type application/pdf, not through the MCP connection. It also explains expiration via expires_in and that the stored object is durable and always a .pdf.

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 front-loaded with purpose, then flows into the exact upload steps and downstream integration. Every sentence carries operational value, including the Content-Type requirement, MCP bypass warning, and expiration note.

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?

Given that an output schema exists, the description provides the necessary workflow detail for correct invocation: how to upload, where to use public_url, and how long upload_url lasts. The main gap is that it does not explain workspace_id or mention any permission/auth context for the workspace.

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 0%, so the description must compensate. It explains filename as being only for the caller's reference, which is useful, but it does not explain the required workspace_id parameter, leaving one of the two input parameters undocumented.

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 operation and resource: get a presigned URL to upload a PDF for a DM automation. It clearly distinguishes this PDF upload workflow from generic uploads by tying the result to a downloadable PDF asset used by automations.

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?

It gives clear usage context: use this to attach a downloadable PDF to an automation, then pass public_url into a dm_buttons entry with kind="pdf" via create_automation or update_automation. It does not explicitly name when not to use it or alternatives such as a video upload tool, but the intended workflow is clear.

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