Skip to main content
Glama

Attach the user's own image to a post

flypost_attach_post_image

Put an image the USER gave you (their photo, screenshot, or a graphic made in Canva or Figma) onto a post draft: image_base64 + content_type, or a source_url (re-hosted in their Flypost storage, so it is still there when the post publishes). PNG, JPEG, WEBP or GIF, max 10MB. A text post gets it added to its photos (call again to add more); a concept post has its generated visual replaced (replaced_asset_url comes back). A carousel gets nothing attached: you get a hosted image_url back for flypost_upload_slide_image (source_url). Only images the user actually gave you: to make one use flypost_create_post_image, and never use it to place a brand logo. flypost_list_post_images and flypost_remove_post_image manage what is attached.

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": {
      "draft_id": "<draft_id>"
    },
    "name": "flypost_attach_post_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYes
file_nameNoOptional original file name, used in storage.
source_urlNoFetch the image from this url instead of passing bytes.
content_typeNoWith image_base64: MIME type, e.g. image/png.
image_base64NoBase64-encoded image bytes (a data: URL is also accepted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing the mutating effect per draft type: text posts append to photos (repeat calls add more), concept posts replace the generated visual and return replaced_asset_url, carousels are untouched. It also explains the re-hosting behavior of source_url so the image survives until publish, and states the format and 10MB size limits — none of which the annotations provide.

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 action and accepted inputs, then the conditional outcomes, then the guardrails and related tools — a logical order with no filler. It is dense with parenthetical asides, but each carries substantive constraint information rather than padding.

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?

There is no output schema, yet the description compensates by naming the return values an agent must act on (replaced_asset_url, hosted image_url for flypost_upload_slide_image). Combined with the per-draft-type branching and the source-of-image constraint, an agent has everything needed to call it correctly on the first try.

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 80% and the description still adds real meaning: it explains the two mutually exclusive input paths (image_base64 + content_type versus source_url), that source_url images are re-hosted into Flypost storage, and the accepted formats and size cap. It does not clarify file_name, but the schema already documents that parameter adequately.

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 ("Put an image ... onto a post draft") and immediately scopes what counts as acceptable input (user's own photo, screenshot, or Canva/Figma graphic). It distinguishes itself behaviorally from the sibling generators by naming flypost_create_post_image as the tool for creating images rather than attaching them.

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?

Gives explicit exclusions and alternatives: "Only images the user actually gave you: to make one use flypost_create_post_image, and never use it to place a brand logo," plus routing to flypost_list_post_images and flypost_remove_post_image for management. It also pre-empts a likely wrong call by telling the agent a carousel gets nothing attached and to use flypost_upload_slide_image instead.

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.