Skip to main content
Glama

Browse the project's images

flypost_list_media
Read-only

The project's media library: carousel slide images (current and earlier versions), generated post images and article covers, newest first, each with its url and where it came from. Any of them can go on a carousel slide with flypost_upload_slide_image (source_url). Look at one with flypost_view_visuals on its concept.

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_list_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNoDefault 60.
project_idNoProject id; omit for the active project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so this is a safe read. The description adds useful behavior: results are ordered newest first, they include earlier versions of slide images, and each item carries its url and origin. It says nothing about pagination behavior or how to page past the limit; with annotations covering safety, this lands at an adequate 3.

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 resource and its contents, with no filler. The follow-up sentences on the upload and visual-viewer chaining earn their place. Slightly dense in one long opening clause, but nothing is wasted.

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

Completeness3/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 carries the burden of return shape; it does name the key fields (url, origin) and ordering, which is helpful. But for a tool with a filtering enum and a limit param, it leaves out how filtering and limits shape the result set, which an agent needs in order to call it correctly.

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 coverage is 67%: project_id and limit (default 60) are documented in the schema, but the kind enum has no description there. The description's three categories (slide images, post images, article covers) loosely map to the slide, post_image, and article_cover enum values, which hints at filtering, but it never states that kind restricts the results or how limit interacts with the newest-first ordering. Baseline 3 for mostly-covered schema is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and its contents: 'The project's media library: carousel slide images (current and earlier versions), generated post images and article covers, newest first.' An agent knows exactly what it gets. However, it never distinguishes itself from siblings like flypost_list_post_images or flypost_list_logos, which are separately listed as contexts, so sibling differentiation is only implicit.

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

Usage Guidelines4/5

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

It gives clear downstream guidance for using the results: 'Any of them can go on a carousel slide with flypost_upload_slide_image (source_url)' and 'Look at one with flypost_view_visuals on its concept.' That is real context on what to do next. It lacks any explicit when-not guidance or named alternative for retrieving images from a different scope.

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.