Skip to main content
Glama

Add a screenshot

add_screenshot

Add a screenshot to a launch: a png, jpg or webp up to 5 MB, either as a public https image_url or as image_base64. The first screenshot is the cover. Use real screenshots of the product, never made-up ones.

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": {
      "id": "<id>"
    },
    "name": "add_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe launch id
image_urlNoa public https address of the image
image_base64Nothe image file, base64 encoded

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: accepted formats (png, jpg, webp), a 5 MB cap, two mutually exclusive input modes, and the non-obvious side effect that the first screenshot becomes the cover. It does not cover permissions, duplicate handling, or whether the call is reversible.

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 the operation and constraints, with no filler. The closing style/policy sentence is slightly tangential but arguably earns its place by discouraging fabricated image URLs.

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 three-parameter mutation tool with no annotations and no output schema, the description covers the practical essentials: formats, size ceiling, input alternatives, and the cover-image side effect. The remaining gap is the absence of any statement about what the call returns or what happens on failure/duplication.

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 coverage is 100%, so the baseline is 3 and the schema already documents all three parameters. The description does add real meaning the schema lacks — the size and format limits attached to the image inputs and the either/or exclusivity between image_url and image_base64 — but it never explains the required 'id' beyond what the schema says.

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?

The description states a specific verb and resource — 'Add a screenshot to a launch' — so the agent knows exactly what operation it performs. The 'to a launch' scoping implicitly separates it from add_listing_screenshot, but the sibling is never named, so differentiation is inferred from the name 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?

It gives useful in-tool guidance on which input path to take ('either as a public https image_url or as image_base64') and a content policy ('Use real screenshots... never made-up ones'). What is missing is routing guidance against alternatives — nothing says when to pick this over add_listing_screenshot or whether a launch must already exist.

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