Skip to main content
Glama
Sign In
glongus-mcp

glongus-mcp

by glongusmain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Copy a photo onto a listing from a web address

add_listing_photo_from_url

Fetch a public HTTPS image (JPEG/PNG/WebP, max 5MB) and attach it to an existing listing, up to six photos, for migrating item photos from marketplace pages.

Instructions

Fetch a public image (https, max 5MB, jpeg/png/webp) and add it to one of your listings (max 6 photos). For moving your owner’s own listing over from eBay, Vinted or similar: read their listing page, create the Glongus listing, then pass each photo’s image URL here. Only for photos of your owner’s own item. Requires GLONGUS_API_KEY.

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": {
      "listing_id": "<listing_id>",
      "photo_url": "<photo_url>"
    },
    "name": "add_listing_photo_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
photo_urlYesDirect https URL of the image
listing_idYesListing id to attach the photo to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4.1/5.0
Behavior4/5

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

With annotations only declaring the generic mutation profile, the description carries real weight: auth requirement (GLONGUS_API_KEY), per-image constraints (https, max 5MB, jpeg/png/webp) and the 6-photo cap on the listing. It is silent on behavior at the cap or when the fetch fails (no return value, no duplicate handling), and there is mild tension with openWorldHint=false given it fetches arbitrary remote URLs.

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 sentences, front-loaded with the core action and limits, then the migration scenario, then the eligibility and auth caveat. Every clause carries a constraint or a use condition; nothing is restated from the schema or annotations.

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 mutation with no output schema, the agent knows what it does, the format/size limits, the photo ceiling, the required credential, and the intended workflow. Remaining gaps are failure modes and what is returned on success, which are minor for this complexity.

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 would be 3, but the description adds constraints on photo_url that the schema does not encode: https-only, 5MB ceiling, and accepted formats. It adds nothing for listing_id beyond what the pattern and description already say.

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?

"Fetch a public image ... and add it to one of your listings" states a specific verb and resource, and the phrase "from a web address" in the title plus "pass each photo's image URL here" implicitly separates it from the sibling add_listing_photo (binary upload). It stops short of naming that sibling explicitly, so an agent must infer the boundary from the URL wording.

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 a concrete when-to-use scenario (migrating the owner's own listing from eBay/Vinted, with an ordered workflow: read their page, create the listing, then pass URLs) and an explicit exclusion ("Only for photos of your owner's own item"). It does not point at alternatives for other photo sources, so it is clear context without full routing.

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

Deploy Server

Other Tools