EmailFig

Add image from URL

upload_image_from_url

Adds an image from a public https address to the account's image library and returns it. PNG, JPEG or GIF, under 10 MB. Use its url as an image block's src.

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": {
      "url": "<url>"
    },
    "name": "upload_image_from_url"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The image's own https address, not a page that shows it.
`alt_text`	No	What the image shows.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, open-world write, so the bar is lower; the description still adds real constraints: source must be public, https-only, limited to PNG/JPEG/GIF, and under 10 MB. It omits what happens on duplicate or failed fetches, but covers the operationally important limits.

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?

Three short sentences, front-loaded with the action, then the constraints, then the usage hint. No redundant restatement of the title or name.

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 two-parameter upload tool with no output schema, the definition covers input constraints and states that the image is returned. It could say more about the returned identifier or failure modes, but an agent has enough to invoke it correctly.

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 both parameters are documented, including the useful 'not a page that shows it' clarification on url. The description adds only the word 'public' and file-type/size limits, so it neither compensates nor needs to.

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 first sentence gives a specific verb and resource ('Adds an image from a public https address to the account's image library and returns it'), which is unambiguously distinct from the sibling list_images. The final sentence even states what the result is used for.

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 states the input condition (public https address, PNG/JPEG/GIF, under 10 MB) and the downstream use ('Use its url as an image block's src'), which tells the agent where this fits in a workflow. It does not name alternatives or say when not to use it, so it falls short of explicit routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All EmailFig tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.