Skip to main content
Glama

List the images on a post

flypost_list_post_images
Read-only

List the images on a post draft: its attached photos (from flypost_attach_post_image or flypost_create_post_image) and the visual it publishes with. Use the image_url values with flypost_remove_post_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": {
      "draft_id": "<draft_id>"
    },
    "name": "flypost_list_post_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish this is a safe, non-destructive, closed-world read, so the bar is lower. The description does add useful behavioral detail about the two categories of images returned and that image_url is the identifier needed for removal. It omits what a draft with no images returns and gives no hint about ordering or completeness of the list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both earning their place: the first defines the resource and its contents, the second routes the returned values to the removal tool. Scope and output are front-loaded with no filler or repetition of the title.

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 one-parameter read with no output schema, the description does cover what is returned (attached images plus the publishing visual) and how the returned url is used downstream. It stops short of describing the response shape (whether each image has ids, order, or a type discriminator) and says nothing about the single input, which keeps it from being fully self-sufficient.

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

Parameters2/5

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

There is a single parameter, draft_id, and schema description coverage is 0%, so the description must carry the meaning. It only implies that the id names a 'post draft' and never says where to obtain one (e.g., via a list-drafts tool) or what format it takes. That is a meaningful gap for a tool whose only input is undocumented in the schema.

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 ('List the images on a post draft') and enumerates exactly what comes back: attached photos from flypost_attach_post_image/flypost_create_post_image plus the visual published with the post. That level of specificity distinguishes it from sibling list tools such as flypost_list_media without requiring the schema to be opened.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies its role in a workflow by naming flypost_remove_post_image as the consumer of the returned image_url values, which is actionable. But it never states when to choose this over alternatives (e.g., flypost_list_media) or any precondition such as the draft already existing or being in a postable state, so guidance is implied rather than 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.