Skip to main content
Glama

Get a link to upload pictures

email_image_upload_link

Makes a one-time Hollerpost page where the person can upload pictures from their own device (up to 10, JPEG, PNG, WebP or GIF, 5 MB each). Use it when the person has a picture you cannot pass as a public URL or base64, for example one they dropped into this chat. Give them upload_url, wait until they say they are done, then call email_images_list with the link_id to get each picture's URL. The link works once and expires after 30 minutes. Sends nothing. Requires API key scope: draft.

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": "email_image_upload_link"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations only declare the generic profile (not read-only, not destructive, not idempotent, closed-world). The description adds what they cannot: the link is single-use, expires after 30 minutes, accepts up to 10 files at 5 MB each in four formats, sends no email despite the 'email_' name, and requires the 'draft' API key scope. These are exactly the facts an agent needs before calling it.

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?

Front-loaded with the effect, then constraints, then the call sequence, then the safety caveat ("Sends nothing") and scope requirement. Every sentence carries information the agent needs; nothing is redundant with the schema or annotations.

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?

No output schema exists, so the description supplies the return contract (upload_url, link_id) and the multi-step human-in-the-loop flow. For a zero-parameter, non-idempotent link-generation tool, no material gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero input parameters, so the schema baseline is 4. The description goes further by describing the values produced and consumed downstream — upload_url handed to the person and link_id passed to email_images_list — which gives the agent the contract the tool participates in even without an output schema.

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 resource (a one-time Hollerpost upload page) and what it enables (a person uploading pictures from their own device). It also distinguishes this tool from the alternative path of passing a public URL or base64, so the agent can tell which tool applies without inspecting siblings.

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?

Explicit trigger condition is given ("Use it when the person has a picture you cannot pass as a public URL or base64"), plus the exact follow-up sequence: hand over upload_url, wait for confirmation, then call email_images_list with the link_id. This names the companion tool and the ordering constraint.

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