Skip to main content
Glama

Set an image from a URL

set_image_from_url
Destructive

Put an existing picture from a public web address on an ebook: as its cover image (cover: true), into an image block (blockId), or as a new image after a block (afterBlockId, with optional alt and caption). PNG, JPEG, WebP or GIF up to the editor's size limit; SVG is not accepted. Use pictures the user owns or may use. Replacing an image that is already there needs replaceExisting: true.

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

Input Schema

NameRequiredDescriptionDefault
altNoAlt text describing the picture, for a body image.
urlYesA public https:// address of a PNG, JPEG, WebP or GIF picture.
coverNotrue: set it as the cover image.
blockIdNoFill this existing image block (get_ebook gives block ids).
captionNoA caption under a NEW body image.
projectIdYesThe ebook (list_ebooks gives ids).
afterBlockIdNoInsert a new image after this block (after its caption, for an image).
replaceExistingNotrue to replace an image the block or cover already has.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false. The description adds valuable context beyond that: accepted formats (PNG, JPEG, WebP, GIF; SVG not accepted), a reference to the editor's size limit, the requirement to set replaceExisting: true when overwriting, and the ownership/usage restriction. It does not disclose auth requirements or error behavior, but the added format and replacement details are meaningful.

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?

Two tightly written sentences, front-loaded with the core action and explicitly mapped to the parameter-based modes. Every clause contributes useful information (placement options, format constraints, replacement flag), and there is no filler or redundancy.

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?

With 8 parameters, 100% schema coverage, no output schema, and annotations covering safety traits, the description supplies the remaining critical context: supported formats, size limit hint, replacement requirement, and legal usage. It could be slightly more complete by mentioning authentication or failure behavior for invalid URLs, but it is sufficient for correct invocation.

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%, so the schema already documents each parameter. The description adds some relational meaning by grouping parameters into three modes (cover, blockId, afterBlockId) and noting that alt and caption apply to new body images. However, it largely restates schema-level details and does not clarify exclusivity or edge cases (e.g., what happens if both cover and blockId are provided), so a baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Put an existing picture from a public web address on an ebook.' It then names the three distinct placement modes (cover, blockId, afterBlockId), leaving no ambiguity about what the tool does. This clearly distinguishes it from sibling tools like create_ebook_from_url or set_brand_theme_logo.

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?

The description gives concrete conditions for each mode: 'as its cover image (cover: true), into an image block (blockId), or as a new image after a block (afterBlockId...).' It also adds a prerequisite for replacement ('Replacing an image that is already there needs replaceExisting: true') and a legal note ('Use pictures the user owns or may use'). It does not explicitly name an alternative tool or state when not to use this tool, which keeps it from a 5.

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