Skip to main content
Glama

Add a NEW brand asset file to project settings

flypost_upload_logo

Add a NEW image to the project's brand settings, where the generators use it: a logo, a product screenshot (asset_type product_reference), a homepage screenshot (homepage_reference) or a profile photo (profile_image). Max 5MB. Returns the asset_url: a product screenshot can then go in a design (flypost_design_visual images). A logo joins the logo library, or becomes the default when the project has none or with make_default. This does NOT put a logo onto a generated image: use flypost_place_logo (image posts) or flypost_carousel_logo (carousels). Check flypost_list_logos first, as most projects already have their logo. Only for a file the user gave you: never fabricate or fetch bytes for it.

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": {
      "image_base64": "<image_base64>",
      "content_type": "<content_type>"
    },
    "name": "flypost_upload_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoA name for it in the library, e.g. 'White logo'.
file_nameNo
asset_typeNologo (the default), product_reference (a product screenshot), homepage_reference (a homepage screenshot) or profile_image (a profile photo).
content_typeYesMIME type, e.g. image/png.
image_base64YesBase64-encoded image bytes (no data: prefix).
make_defaultNoLogos only: make this the default logo (the old one stays in the library).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, closed-world write; the description adds real substance on top: the 5MB size cap, the returned asset_url, and the side effect that a logo joins the logo library or becomes the default. It stops short of stating auth/permission requirements or what happens on a same-name duplicate, which keeps it off 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?

Front-loaded with the core action and asset types, then moves to constraints, return value, and exclusions in a logical order with zero filler sentences. It is dense and reads as one long block, which slightly hurts scannability but not correctness.

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?

With no output schema, the description correctly compensates by naming the return value (asset_url) and its downstream use. For a 6-parameter upload mutation, the size limit, defaults, library behavior, and exclusion rules cover everything an agent needs to call it safely.

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 description coverage is already 83%, so the baseline is 3; the description nonetheless adds downstream meaning the schema lacks, e.g. that a product_reference screenshot can subsequently be used in flypost_design_visual and that make_default leaves the old logo in the library. It does not explain label, file_name, or base64 sizing constraints beyond the 5MB cap.

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 ('Add a NEW image to the project's brand settings') and immediately enumerates the four asset kinds it accepts. It also distinguishes itself from the look-alike siblings by name (flypost_place_logo, flypost_carousel_logo, flypost_list_logos), so an agent can route correctly without opening any 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?

Gives explicit when-to-use (a file the user actually supplied), when-not-to-use ('never fabricate or fetch bytes'), a prerequisite check ('Check flypost_list_logos first, as most projects already have their logo'), and names the correct alternatives for the adjacent intent. This is close to ideal routing guidance.

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.