Skip to main content
Glama

Design a visual (Designed layout)

flypost_design_visual

Design a carousel, an infographic, or a striking_stat or comparison Image post in the user's brand with Flypost Designer (the editor's "Designed layout"), from the words saved on the concept: flypost_save_concept first. The default for those formats; the footer carries the logo or their LinkedIn profile. A carousel comes back as a whole deck with its PDF. To show the user's real screenshot, pass it in images (option product_screenshot puts it in a laptop or phone frame). Blocks 1-5 minutes and is an AI run on the user's image allowance; designing again replaces the design, so change one with flypost_revise_design. Not for meme, product_in_situ or 'Let AI decide' posts (flypost_generate_image).

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": {
      "content_bank_item_id": "<content_bank_item_id>",
      "format": "<format>"
    },
    "name": "flypost_design_visual"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYescarousel, infographic, or the Image post's type: striking_stat or comparison (its image_substyle).
imagesNoUp to 3 images the user wants in the design, from Flypost storage only: a product screenshot url from flypost_get_brand_kit, or an image from flypost_list_media. The designer uses every one.
optionsNoThe editor's design options, only when the user wants them: more_visual (fewer words, one strong graphic), big_number (lead with one number from the data), illustration (a generated picture of one real object), product_screenshot (one of the project's product screenshots in a laptop or phone frame; needs product screenshots in the brand kit), stock_photo (a real stock photo of a place, object or scene the post is about), website_screenshot (a live capture of a real web page the post is about: name the page in direction, e.g. "the Taplio pricing page", or the designer finds it), logos (the logos of the tools and companies the post names). A ticked screenshot that cannot be made is retried once, then left out: check pictures in flypost_view_visuals.
directionNoOptional art direction in a sentence or two, only when the user gave some (e.g. "dark background, lots of space around the number"). Leave it out to let the designer decide.
content_bank_item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations, which only mark it as non-read-only and non-open-world: it discloses a 1–5 minute blocking runtime, that it consumes the user's AI image allowance, that re-running replaces the existing design, that a carousel returns as a whole deck with a PDF, that the footer carries the logo or LinkedIn profile, and that an unmakeable screenshot is retried once then dropped. The destructiveHint=false annotation is not contradicted in a meaningful way, since the overwrite is of the prior generated design and is recoverable via flypost_revise_design.

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 its format scope, then prerequisites, deliverables, cost, and exclusions in a sensible order. Dense and somewhat run-on, with a few clauses that duplicate option text already in the schema, but almost every sentence carries operational information.

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

Completeness4/5

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

With no output schema and a long-running AI generation, the definition covers the essentials: latency, quota consumption, replacement semantics, and the carousel return shape plus where to inspect results (flypost_view_visuals). Return shape for the non-carousel formats (single infographic/stat image) is only implied, which is a minor remaining gap.

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%, so most parameters are already documented; the description adds framing rather than new syntax (e.g. tying images to a real user screenshot and the product_screenshot frame option, and telling the agent to name a page in direction). It also indirectly explains the otherwise undocumented required content_bank_item_id by tying it to the saved concept from flypost_save_concept, which compensates for the coverage gap.

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: design a carousel, infographic, striking_stat or comparison Image post with Flypost Designer ('Designed layout'), derived from a saved concept. It explicitly excludes the neighboring cases ('Not for meme, product_in_situ or "Let AI decide" posts (flypost_generate_image)'), so an agent can route between this and flypost_generate_image 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?

Gives an ordering prerequisite ('from the words saved on the concept: flypost_save_concept first'), declares default status ('The default for those formats'), and names the correct alternative for iteration ('designing again replaces the design, so change one with flypost_revise_design'). Both when-to-use and when-not-to-use are explicit.

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.