Skip to main content
Glama
hostkey-cloud

hostkey-mcp-server

Official
by hostkey-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

s3_get_files

Read-only

List files in a specified S3 bucket with pagination and filename search, so you can locate and page through stored objects.

Instructions

List files in a bucket with pagination and search (s3/get_files).

Input Schema

NameRequiredDescriptionDefault
pageNoIgnored; use search / limit. InvAPI paginates with continuation_token.
limitNoPage size (mapped to InvAPI max_keys, max 100)
s3uidNoS3 account UID; omit only if the token is bound to a single S3 account
bucketYesBucket name
searchNoSearch string by file name
account_idNoDeprecated alias for s3uid / get_users.id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.8
    • changedInput schema / properties / account_id / description
      Previous value: -"Deprecated alias for s3uid"New value: +"Deprecated alias for s3uid / get_users.id"
    • changedInput schema / properties / limit / description
      Previous value: -"Page size"New value: +"Page size (mapped to InvAPI max_keys, max 100)"
    • changedInput schema / properties / page / description
      Previous value: -"Page number"New value: +"Ignored; use search / limit. InvAPI paginates with continuation_token."
  2. Changed2 schema fields changedv1.0.4
    • changedInput schema / properties / account_id / description
      Previous value: -"S3 account ID (if required; check via s3_get_users)"New value: +"Deprecated alias for s3uid"
    • addedInput schema / properties / s3uid
      Added value: +{
+  "description": "S3 account UID; omit only if the token is bound to a single S3 account",
+  "type": [
+    "string",
+    "number"
+  ]
+}
  3. Changed5 schema fields changedv1.0.3
    • changedInput schema / properties / account_id / description
      Previous value: -"ID S3-аккаунта (если требуется; уточняйте через s3_get_users)"New value: +"S3 account ID (if required; check via s3_get_users)"
    • changedInput schema / properties / bucket / description
      Previous value: -"Имя бакета"New value: +"Bucket name"
    • changedInput schema / properties / limit / description
      Previous value: -"Размер страницы"New value: +"Page size"
    • changedInput schema / properties / page / description
      Previous value: -"Номер страницы"New value: +"Page number"
    • changedInput schema / properties / search / description
      Previous value: -"Поисковая строка по имени файла"New value: +"Search string by file name"
  4. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that pagination and search are supported, which is useful behavioral context, but it does not describe return format, pagination mechanics, or operational constraints beyond that.

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?

The description is a single well-formed sentence with the core operation front-loaded and no wasted text. The endpoint reference in parentheses is compact and useful for disambiguation.

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?

Given the fully described schema, read-only and open-world annotations, and no output schema, the description is mostly sufficient for calling the tool. It does not explain pagination mechanics such as continuation_token, but the schema covers the parameter-level details.

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 six parameters, including bucket, search, limit, and the deprecated/ignored page field, are documented in the schema. The description mentions pagination and search at a high level but adds no parameter-level meaning beyond what the schema already provides.

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?

The description states a specific verb and resource: it lists files in a bucket, with pagination and search, and includes the underlying endpoint s3/get_files. This distinguishes it from nearby S3 tools such as s3_get_buckets, which lists buckets rather than files.

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?

The intended use is implied by 'List files in a bucket with pagination and search', but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent can infer this is for file listing within a bucket, but the description does not route it among alternatives.

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

Deploy Server

Other Tools