Skip to main content
Glama

List the files on a Flowershow site

list-files
Read-only

List the files currently on one of the signed-in user's Flowershow sites: each path, its size in bytes and when it last changed. Use it before updating a site in a new conversation, to see which pages exist, pick the right paths to update or delete, and avoid duplicating a page under a new name. Get siteId from list-sites. Returns up to 1000 paths; for bigger sites, pass folder to list one folder at a time. If the user is not signed in yet, calling it asks them to sign in to Flowershow first.

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": {
      "siteId": "<siteId>"
    },
    "name": "list-files"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNoOnly list files in this folder (and its subfolders), e.g. "blog"
siteIdYessiteId of the site, from list-sites

Output Schema

NameRequiredDescriptionDefault
filesYes
totalYes
siteIdYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real context beyond them: a 1000-path return cap with the folder-scoping workaround, and that unauthenticated calls prompt a sign-in flow. It does not disclose ordering or pagination semantics beyond the cap.

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 purpose and return fields, then a use-case sentence, then operational limits and the auth note. The middle sentence is dense but every sentence carries information, with no filler.

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?

An output schema exists, so return values needn't be explained, yet the description still summarizes them. Prerequisite (list-sites), scale limit (1000 paths), the folder workaround, and auth behavior are all covered. Minor gaps remain, such as file ordering and whether deleted or special entries are included.

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 100% and both parameters are documented there, including folder's "and its subfolders" semantics, so the schema does the heavy lifting. The description reinforces folder as the escape hatch for >1000-path sites and states siteId's provenance from list-sites, which is useful but largely duplicative.

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?

Specific verb+resource+scope: lists files on one of the signed-in user's Flowershow sites and enumerates what each entry contains (path, size in bytes, last-changed time). Distinguishable from siblings such as list-sites (sites, not files) and read-file (content, not listing).

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?

Explicit when-to-use: before updating a site in a new conversation, to see which pages exist, pick paths to update or delete, and avoid duplicating a page. Also gives the prerequisite chain to list-sites for siteId and an explicit workaround (pass folder) for sites over 1000 paths.

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.