Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_media_list_files

Read-onlyIdempotent

Retrieve a paginated list of files and folders from media storage. Filter by type, location, sort order, and more to manage media assets.

Instructions

Regression check (old connector 422'd here because it had no way to pass the required type param): VERIFIED FIXED — type, altType, altId, sortBy, sortOrder are all present and required in this tool's input schema, matching the spec. Get List of Files/ Folders Fetches list of files and folders from the media storage Endpoint: GET /medias/files (Version header: v3; source: v3/medias-v3.json) OAuth scopes: medias.readonly Pagination params: offset, limit — pass them to page through full result sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesType
altIdYeslocation Id
limitNoNumber of files to show in the listing
queryNoQuery text
offsetNoNumber of files to skip in listing
sortByYesField to sorting the file listing by
altTypeYesAltType
fetchAllNoFetch all files or folders
parentIdNoparent id or folder id
sortOrderYesDirection in which file needs to be sorted
Behavior4/5

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

Annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint false) already indicate safe read operation. Description adds value by mentioning pagination with offset/limit and OAuth scopes (medias.readonly). This enhances transparency beyond annotations.

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

Conciseness2/5

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

Description is cluttered with an irrelevant regression check note at the beginning ('Regression check...'), which does not help an AI agent. The core purpose is buried. Should be front-loaded with the main functionality.

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 10 parameters, 5 required, and no output schema, the description provides endpoint, OAuth scopes, and pagination hint, but lacks explanation of response structure or detailed parameter roles. The regression note wastes space.

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 100%, so all parameters have descriptions. Description mentions pagination params (offset, limit) but does not add meaning beyond what schema provides. No additional clarification for required parameters.

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?

Description clearly states 'Get List of Files/ Folders' and 'Fetches list of files and folders from the media storage'. The verb 'Fetches' and resource 'list of files and folders' are specific, and the tool is distinct from siblings like upload, delete, or update operations.

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?

Description implies usage for listing files/folders but does not explicitly state when to use versus alternatives, nor does it provide when-not or alternative tool recommendations. OAuth scopes and pagination notes are helpful but not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zackscriven/ghl-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server