Skip to main content
Glama

Add an email image

email_image_upload

Stores an image on Hollerpost for use in an email and returns its https URL. Pass url (a public https image, for example from the business website) or data_base64 (the file itself). For a picture the person has on their device or dropped into the chat, use email_image_upload_link instead. JPEG, PNG, WebP or GIF, up to 5 MB (GIFs up to 2 MB). Hollerpost shrinks it to at most 1200px wide and saves it as JPEG, or PNG when it has transparency, so the returned type can differ from the upload. Emails link to the image rather than attaching it, so it adds nothing to the message size. Limits: 100 uploads per API key per 24 hours and 500 per workspace per 30 days, so upload each picture once and reuse its url. Use the returned url in image_url, a section image_url, or an image line in body_md: What it shows. 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPublic https URL of the image to copy.
filenameNoA file name, for example "junior-cues-banner.png".
data_base64NoThe image file, base64 encoded (a data: URL prefix is fine).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare the generic safety profile (readOnlyHint false, destructiveHint false, idempotent false); the description adds the substantive behavior: server-side re-encoding to JPEG/PNG with a 1200px cap so the returned type can differ, that nothing is sent, that emails link rather than attach, and the API-key scope 'draft'. It also discloses concrete rate limits (100 per key per 24h, 500 per workspace per 30d), which is exactly the operational context an agent needs before retrying.

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-loads what the tool does and returns, then input choice, format limits, transformation behavior, then constraints and usage of the result. Dense but every sentence carries actionable information with no restatement of the title or schema.

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, but the description covers the return value (https URL, possibly a different image type) and how to consume it, plus size/format limits and quotas. Nothing an agent needs to invoke this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning by explaining what each input path represents and when to choose one over the other ('a public https image, for example from the business website' vs 'the file itself'). It does not describe the filename parameter, leaving that to the 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?

States a specific verb and resource ('Stores an image on Hollerpost ... returns its https URL') and immediately distinguishes itself from the sibling email_image_upload_link by naming the case that tool covers. An agent can pick between the two 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?

Gives explicit when-to-use for each input path (url for a public https image, data_base64 for the file itself) and explicitly routes device/chat pictures to email_image_upload_link. It also tells the agent where the result goes (image_url, section image_url, or body_md image line) and warns to upload once and reuse the url.

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