Skip to main content
Glama

Place the logo on an image post

flypost_place_logo

Put the brand logo on an image or infographic post, as the editor's "Add logo" does: the image fills the 1080x1350 canvas, the logo goes at tl, tc, tr, bl, bc or br (54px from the edges), logo_size canvas px wide (32-640; 120-200 suits most wordmarks, smaller for a square brandmark). Placing again re-bakes from the original, so logos never stack. Pick a corner clear of text and the subject, and a logo version (flypost_list_logos) that contrasts, then check with flypost_view_visuals. An infographic drawn with its logo is refused unless you looked and pass drawn_logo_check 'absent'. Needs a post draft (flypost_create_draft). Not for Designed layouts, which carry the brand already, or carousels (flypost_carousel_logo).

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>",
      "position": "<position>"
    },
    "name": "flypost_place_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
logo_idNoFrom flypost_list_logos; default 'default'.
draft_idYes
positionYes
logo_sizeNoLogo width in canvas px (the canvas is 1080 wide). Default 120.
drawn_logo_checkNoOnly for an image generated with the logo drawn in: you looked (flypost_view_visuals) and the brand's name and logo are NOT on it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare the mutation/no-open-world profile; the description adds the key behavioral trait that 'Placing again re-bakes from the original, so logos never stack', i.e. idempotent re-application. It also discloses a refusal condition (infographics with a drawn logo are rejected unless drawn_logo_check 'absent' is passed after visual inspection) and concrete geometry (54px insets, 1080x1350 canvas). Nothing contradicts the annotations.

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?

The action and scope are front-loaded and every clause carries operational information, but the single dense paragraph packs several distinct concerns (geometry, idempotency, prerequisites, refusal rule, exclusions) into run-on sentences with heavy parentheticals. Slightly hard to scan, though not padded.

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 mutating tool with no output schema, the description supplies everything an agent needs: prerequisite draft, how to source the logo, placement/size guidance, the re-bake semantics, and the only failure mode worth pre-empting (drawn-logo refusal). No significant gap remains.

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?

With only 60% schema coverage, the description carries the load and does: it explains logo_size in practical terms (32-640 with 120-200 suiting wordmarks, smaller for square brandmarks), clarifies the position enum's meaning via the 54px edge offset, and explains when drawn_logo_check is legitimate. This is meaning well beyond the schema text.

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?

The description opens with a specific verb and resource ('Put the brand logo on an image or infographic post') and immediately delimits scope by naming what it is not for: Designed layouts (which already carry the brand) and carousels (flypost_carousel_logo). An agent can distinguish this from sibling logo tools without opening either 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?

It gives explicit routing: prerequisite 'Needs a post draft (flypost_create_draft)', logo selection via flypost_list_logos, verification via flypost_view_visuals, and hard exclusions for carousels and Designed layouts. It also states the decision heuristic ('Pick a corner clear of text and the subject... that contrasts'), which is a when-to-use rule rather than just a description.

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.