Skip to main content
Glama

Add an image the chatbot can show

add_image

Add an image the chatbot may show. The description is what the AI reads to decide when the image answers the question, so describe what it shows and when it helps. Needs the Standard plan or higher, and a website can hold up to 100 images.

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": {
      "image_url": "<image_url>",
      "description": "<description>"
    },
    "name": "add_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_urlYesAddress of the image.
website_idNoNumeric id of the website, from list_websites. Omit to use the account's primary website.
descriptionYesWhat the image shows and when the chatbot should send it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, open-world mutation, and the description adds real behavioral context beyond them: a plan gate and a per-website quota of 100 images. It stops short of saying what happens on a duplicate or invalid image_url.

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 short sentences, front-loaded with purpose, then authoring guidance, then constraints — no filler. The second sentence is slightly instructional in tone but still earns its place by shaping how the key parameter is written.

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 3-parameter creation tool with full schema coverage, no output schema, and annotations covering the safety profile, this is close to complete: purpose, plan gate, quota, and how to write the description are all present. The main missing piece is return behavior (e.g., whether an id comes back) for a subsequent delete_image call.

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 the baseline is 3, but the description goes further by explaining the downstream consequence of the description parameter — the AI reads it to decide when the image answers a question. That is genuine meaning beyond the schema's restatement, though image_url and website_id get no extra treatment.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Add an image the chatbot may show") and the qualifier "chatbot may show" hints at the distinction from knowledge-text tools. It does not explicitly name siblings like add_knowledge_text or list_images, so differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Includes useful preconditions (Standard plan or higher, 100-image cap per website) and explains how to author the description field, but never says when to choose this over add_knowledge_url or add_knowledge_text, or that delete_image/list_images are the counterpart operations.

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