Skip to main content
Glama

Cluby MCP

by com.cluby.api
OverviewDiscussionsAdmin

Import image

import_image

Import a photo from a public https URL into the organization's image storage, the same as picking an image in the Partner Hub. Returns originalUrl and image; pass image unchanged as a benefit's content.image in create_benefit or update_benefit, which wait for the processed versions before saving. Only images imported this way are accepted by the benefit write tools; a birthday gift takes the originalUrl as content.imageUrl.

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https URL of the image
orgIdNoOrganization public id, the `id` field from list_orgs. Omit it when the API key reaches exactly one organization.
attributionNoPhotographer credit for an Unsplash photo. Kept on every processed version so the credit travels with the image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / attribution / properties / license
      Added value: +{
+  "description": "Wikimedia only, e.g. \"CC BY-SA 4.0\"",
+  "type": "string"
+}
    • addedInput schema / properties / attribution / properties / licenseUrl
      Added value: +{
+  "format": "uri",
+  "type": "string"
+}
    • removedInput schema / properties / attribution / properties / source / const
      Removed value: -"unsplash"
    • addedInput schema / properties / attribution / properties / source / enum
      Added value: +[
+  "unsplash",
+  "pexels",
+  "wikimedia"
+]
    • changedInput schema / properties / attribution / required
      Previous value: -[
-  "source",
-  "photoId",
-  "photographerName",
-  "photographerProfileUrl",
-  "sourceUrl"
-]New value: +[
+  "source",
+  "photoId",
+  "photographerName",
+  "sourceUrl"
+]
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only give openWorldHint and destructiveHint=false, so the description must carry the behavioral burden. It does: return values (`originalUrl`, `image`), the fact that benefit writes wait for processed versions, and the acceptance constraint on which images benefit tools will take. Missing: what happens on invalid/unreachable URLs, size/format limits, or whether imports are idempotent.

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?

Front-loaded with the purpose, then build in the downstream contract in order of use. Dense but every clause carries decision-relevant information; slightly packed in the final sentence where `originalUrl`/`imageUrl` pairing takes effort to parse.

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, so the description usefully names the returned fields and their downstream role. For a 3-param tool with fully documented nested schema, the remaining gap is failure behavior (bad URL, license/attribution rejection), a minor but real omission.

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?

With 100% schema coverage the baseline is 3, but the description adds cross-tool semantics the schema cannot: pass `image` unchanged into a benefit's `content.image`, and use `originalUrl` as `imageUrl` for gifts. It does not restate `url`/`orgId`/`attribution` rules, which the schema already covers well.

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?

States a specific verb+resource (import a photo from a public https URL into the organization's image storage) and anchors it to a familiar operation (picking an image in the Partner Hub). No sibling tool does this; the identity is unambiguous.

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

Usage Guidelines5/5

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

Explicitly says the tool is a prerequisite for the benefit write tools: only images imported this way are accepted by create_benefit/update_benefit, and birthday gifts take `originalUrl` as `content.imageUrl`. This is exactly the when-to-use vs alternatives guidance an agent needs.

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

All Cluby MCP 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