Skip to main content
Glama

List email images

email_images_list
Read-onlyIdempotent

Lists images already stored on Hollerpost for this workspace, newest first, with their URLs, so you can reuse one instead of uploading it again. Pass link_id (from email_image_upload_link) to get just the pictures uploaded through that link, and whether the person has used it yet. Free and read only. Requires API key scope: read.

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_images_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent images (default 20).
link_idNoThe link_id from email_image_upload_link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety bar is low, yet the description still adds non-trivial context: cost ('Free') and an authorization prerequisite ('Requires API key scope: read'), plus ordering and that results include URLs and per-link usage status. Pagination behavior beyond the limit parameter is not described, keeping it below top marks.

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?

Three tightly packed sentences that front-load the purpose, then the filter, then the cost/auth constraints. 'Free and read only' partially restates the readOnlyHint annotation, which is the only mildly redundant content.

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 2-parameter, zero-required read tool with no output schema, the description covers what is returned (image URLs, newest first, usage status per link), how to filter, and the permission scope required. Only result volume/pagination expectations are left unstated, a minor gap.

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 is 3; the description earns credit for explaining what link_id actually does semantically — filters to pictures uploaded through that link and reveals whether the recipient has used it. It does not add anything for limit, but that parameter is already fully documented in 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 ('Lists images already stored on Hollerpost for this workspace') plus scope, ordering ('newest first') and payload ('with their URLs'). It also positions the tool against the upload siblings by framing its value as reusing an existing image 'instead of uploading it again', so an agent can distinguish it from email_image_upload and email_image_upload_link.

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?

Gives a clear usage motivation (reuse an existing image rather than re-upload) and an explicit conditional path: pass link_id to narrow to pictures uploaded through a specific link. It stops short of naming a hard alternative/exclusion (e.g. 'use email_image_upload if nothing matches'), leaving that to inference.

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