Skip to main content
Glama

Make a share card

make_card
Idempotent

Make the cover-led share card for a moment, a square one and a tall one, into the artist's Library: the release's cover, the artist's name and the moment's words, on the cover's own colors. Made from the artist's cover and name, no AI. Free. Made once per moment and kept: asking again gives the same cards. The moments: out_now: a release that is out, "Out now" over its cover (release_id). still_on_repeat: a release out for a while, "Still on repeat" and the day it came out (release_id). meet: "Meet the artist" with the artist's genre and hometown, on the cover of release_id, else of their newest release. show: a show from list_events, its city, day and venue (event_id), on the cover of the release the show is for, else release_id. milestone: the artist's newest Good news (a listener count passed, a playlist add), or the newest about release_id. Put a card on a picture post with add_post or update_post (media_asset_id).

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": {
      "moment": "<moment>"
    },
    "name": "make_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
artistNoOnly when you are connected as a label: the roster artist this call is for — their artist_user_id from list_roster, or their exact artist name. Required for every artist tool on a label connection. Leave it out on an artist's own connection.
momentYesWhich moment the card is for.
event_idNoFor a show: the show (list_events).
release_idNoThe release (list_releases): required for out_now and still_on_repeat; for the others, whose cover leads the card.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior, and the description adds meaningful context beyond them: no AI generation, free of cost, cards are persisted in the Library, and re-asking per moment yields the same cards. It does not cover upload timing or any failure modes, which keeps it short of a 5.

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 and every clause carries content, but the moment enumeration is a dense colon-chain with embedded quoted strings that takes effort to parse. The size is defensible given five distinct modes, though it could be broken into cleaner lines.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers output shapes, storage destination, idempotency, cost, per-mode inputs, and the exact follow-up call. With no output schema, the description still tells the agent enough about the returned cards to chain into add_post or update_post, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds semantics the schema cannot express: it maps which moment values make release_id required versus optional, and explains that event_id supplies a city, day and venue while release_id selects the cover. This is genuinely load-bearing routing information beyond the flat field descriptions.

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 and artifact (make the cover-led share card), names the two output shapes (square and tall), the destination (the artist's Library), and enumerates the five moment types with what each one renders. An agent can distinguish this from sibling tools like add_post without opening the schema.

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?

Each moment value is tied to its own selection rule and required identifier (out_now and still_on_repeat need release_id, show needs event_id plus a cover source, meet and milestone have explicit fallbacks). It also names the downstream step explicitly: put the card on a picture post with add_post or update_post via media_asset_id.

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