Skip to main content
Glama
Sign In

LivePublicator

by com.livepublicator
OverviewDiscussionsAdmin

Add a cover image

add_image
Idempotent

Adds a cover image to a draft press release. Send an image URL, or a file the user attached in the chat. With neither, it returns a one-time upload link where the user can drop the image. An image 1200 px wide or more fills the page, and from 600 px it shows at its own size. Under 600 px, or without an image, the release uses a simple cover with the company logo and headline, so this step is optional.

Input Schema

NameRequiredDescriptionDefault
image_urlNoA public https URL of the image.
image_fileNoA file the user attached in the chat.
release_idYesThe release id.
image_is_aiNotrue when the image was made with AI. The page then labels it "Illustration, created with AI".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / image_is_ai
      Added value: +{
+  "description": "true when the image was made with AI. The page then labels it \"Illustration, created with AI\".",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, idempotent). The description adds real behavior nowhere in the structured fields: with no image supplied the call returns a one-time upload link, and it explains downstream rendering thresholds (1200 px, 600 px, under 600 px fallback to a logo cover).

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?

Purpose is front-loaded in the first sentence, then input options, then a one-line sizing/fallback rule. Every sentence carries information, though the sizing detail is the least essential and the block runs slightly long.

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?

No output schema exists, so the description usefully covers the non-obvious return case (one-time upload link) and the optionality of the call. Combined with annotations that cover mutation safety, an agent has enough to invoke this correctly; the draft-release-only constraint could be stated more explicitly.

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 description coverage is 100%, so the baseline is 3, but the description goes beyond the per-field schema text by spelling out the branching logic between image_url, image_file, and the neither-case. image_is_ai is left to its schema description, which is adequate.

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 opening sentence names a specific verb and resource ("Adds a cover image") plus the scope ("a draft press release"), which separates it from create_release/update_release/publish_release. It doesn't explicitly name a sibling to route against, so it falls just short of the top tier.

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 gives concrete usage context: pass an image_url, pass a chat-attached file, or pass neither to get a one-time upload link, and it explicitly states the step is optional. No explicit when-not-to-use or named alternative tool, but the conditions are clear.

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

All LivePublicator toolsInspect
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.

Resources