Skip to main content
Glama

Post to BudgetPixel Feed

create_social_post
Destructive

Publish a post to the user's PUBLIC BudgetPixel community feed — visible to everyone and labeled "via MCP". ONLY use this when the user EXPLICITLY asks to post/share/publish; never post proactively. Costs 10 credits per post (anti-spam, charged on publish — same as the developer API) with an hourly posting cap. media: 1–6 images, or 1 video + up to 3 images, or exactly 1 audio track — pass the URLs you got from generations (check_generation_status links) or upload_media, or any public URL/base64. Images can carry optional model/prompt generation info. Audio posts accept song_name, genre (a fixed list — see the enum), lyrics, AND cover_image (cover art goes in its own field, never as a second media item). To enter the post in one of the user's clan themes, pass theme_id (call list_my_themes to find it). Posts are All Rights Reserved by default; pass license ("cc-by" or "cc0") ONLY when the user explicitly asks for a Creative Commons license — it is permanent and cannot be changed after publishing. Returns the public post URL — share it with the user. Posts are moderated after publish (NSFW/spam rating affects feed visibility; the charge is not refunded for hidden posts).

Input Schema

NameRequiredDescriptionDefault
genreNoAudio posts only: the track's genre — EXACTLY one of these values. Omit to have it classified automatically after publishing.
mediaYes1–6 media items. Rules: 1–6 images, OR 1 video plus up to 3 images, OR exactly 1 audio track (audio can't mix).
lyricsNoAudio posts only: lyrics to show with the track.
contentNoThe post's text/caption (optional — media-only posts are fine).
licenseNoOptional content license: "arr" (All Rights Reserved — the default), "cc-by" (CC BY 4.0) or "cc0" (CC0, public domain). OMIT unless the user EXPLICITLY asks for a Creative Commons license — never choose one on their behalf. Permanent: the license cannot be changed after publishing.
theme_idNoOptional: enter the post in a live clan theme — the id from list_my_themes (or the number in a budgetpixel.com/themes/<id> link). Works with any media type; posting to a theme of a clan the user hasn't joined joins them to it, like on the site.
song_nameNoAudio posts only: the track's display name.
cover_imageNoAudio posts only: cover art — an image URL (generation link / upload_media URL), data URI, or base64 (max 15MB). Goes in THIS field, never as a media item.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / license
      Added value: +{
      +  "description": "Optional content license: \"arr\" (All Rights Reserved — the default), \"cc-by\" (CC BY 4.0) or \"cc0\" (CC0, public domain). OMIT unless the user EXPLICITLY asks for a Creative Commons license — never choose one on their behalf. Permanent: the license cannot be changed after publishing.",
      +  "enum": [
      +    "arr",
      +    "cc-by",
      +    "cc0"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / theme_id
      Added value: +{
      +  "description": "Optional: enter the post in a live clan theme — the id from list_my_themes (or the number in a budgetpixel.com/themes/<id> link). Works with any media type; posting to a theme of a clan the user hasn't joined joins them to it, like on the site.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: 10-credit cost charged on publish, hourly posting cap, post-publish moderation with no refund for hidden posts, and the permanence of the license choice. These are exactly the side-effect and cost facts an agent needs for a destructive/open-world write.

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 and the critical 'explicit request only' constraint are front-loaded, and nearly every sentence carries actionable content. It is dense and long, but the padding is minimal and tightly compressed.

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?

For a complex 8-param write tool with no output schema, it covers return value ('Returns the public post URL — share it with the user'), cost, moderation, licensing, and media constraints. An agent can call it correctly without further inference.

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 is 3 and the schema already documents all 8 params. The description still adds cross-field rules not obvious from the schema, e.g. audio cover art belongs in cover_image and must not be a second media item, and the media-combination rules restated concisely.

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 resource ('Publish a post to the user's PUBLIC BudgetPixel community feed') with scope detail (public, visible to everyone, labeled 'via MCP'). No sibling tool does posting, so it is trivially distinguishable from generate_*/upload_media.

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?

Explicit when-to-use ('ONLY use this when the user EXPLICITLY asks to post/share/publish; never post proactively') plus conditional routing to siblings: check_generation_status links / upload_media for media sources, and list_my_themes to find theme_id. The license trigger condition is also spelled out.

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.