Skip to main content
Glama

Look at a post's visuals

flypost_view_visuals
Read-only

See a post's visuals in seconds without rendering: a carousel's slides (role, wording and every slide image), or an image post's published image and its other versions, returned inline for you to look at. Check your own work with it after every generate, design or edit: on brand, readable, no garbled text, no invented logos or screens, the logo visible exactly once. This, not flypost_build_carousel, is how you check a carousel. Pass draft_id for a post (what it publishes) or content_bank_item_id for a concept, then give the user the editor_url.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flypost_view_visuals"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idNo
max_imagesNoHow many images to return; default 10.
content_bank_item_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered by structured data. The description does add real behavior the annotations cannot convey: results come back inline rather than rendered, and the payload differs by post type. It stops short of stating pagination/truncation behavior beyond the max_images cap or the cost of a large image set.

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 value ("in seconds without rendering") and organized as purpose, then QA checklist, then differentiation, then parameters. The middle quality checklist is dense but earns its place as actionable evaluation criteria; the copy is slightly run-on with stacked clauses.

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?

For a three-parameter read tool with no output schema and clean annotations, this covers what the agent needs: the return is inline images, the two id modes are explained, and the required next step (hand the user editor_url) is stated. The one gap is undefined behavior when no id is passed, since required parameters are zero.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, so the schema documents essentially just max_images. The description compensates for the other two by explaining the semantic split: draft_id is a post ("what it publishes") while content_bank_item_id is a concept, which is genuinely useful. It never mentions max_images or what happens when neither id is supplied.

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 ("See a post's visuals"), then enumerates the two content shapes it covers: a carousel's slides with role, wording and every slide image, or an image post's published image and its other versions. It also names the sibling it is not (flypost_build_carousel), so an agent can distinguish intent without opening a 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 explicit trigger ("after every generate, design or edit") and an explicit exclusion ("This, not flypost_build_carousel, is how you check a carousel"). It even supplies the follow-up action ("give the user the editor_url"), leaving nothing to inference about when to reach for this versus a build tool.

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.