Skip to main content
Glama

jfrog_latest_files

Read-onlyIdempotent

Find files in a JFrog Artifactory repository sorted by latest modified timestamp, with filters for path, name pattern, package type, and modification date range.

Instructions

Find latest files by client-side modified timestamp sorting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoRepository-relative path using forward slashes. Omit, empty string, '.', or '/' for the repository root; '..', backslashes, raw URLs, and control characters are rejected.
limitNoMaximum number of results to return. Values below 1 are rejected; values above the configured server limit are clamped.
repo_keyNoOptional repository key to search. Required unless package_type is provided. Raw URLs, path separators, and control characters are rejected.
scan_limitNoMaximum number of matching files to scan before client-side latest-file sorting. Values are clamped to the server AQL scan limit.
name_patternNoOptional file-name pattern for Artifactory AQL matching, such as *.jar or *.zip. Path separators, raw URLs, and control characters are rejected.
package_typeNoOptional Artifactory package type filter. Valid values: bower, cargo, chef, cocoapods, composer, conan, cran, debian, docker, gems, generic, gitlfs, go, gradle, helm, ivy, maven, nuget, opkg, p2, pub, puppet, pypi, rpm, sbt, swift, terraform, vagrant, yum.
modified_afterNoOptional inclusive lower bound for the modified timestamp. Accepts an ISO datetime or YYYY-MM-DD, which expands to the start of that UTC day.
modified_beforeNoOptional inclusive upper bound for the modified timestamp. Accepts an ISO datetime or YYYY-MM-DD, which expands to the end of that UTC day.
include_metadataNoWhether search results should include repo, type, size, and timestamps.
include_full_pathNoWhether search results should include path/name joined as full_path.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare read-only and idempotent behavior, so the description only needs to add extra behavioral context. It adds 'client-side modified timestamp sorting,' which is useful, but does not mention limits, clamping, or other runtime behavior beyond what schema fields imply.

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, tightly worded sentence that conveys the core purpose without any wasted words. It is front-loaded and highly concise.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the rich schema, annotations, and output schema, the description is too minimal for a 10-parameter tool with many siblings. It lacks usage context, prerequisites, or any narrative that would help an agent decide when to invoke it. The schema covers the 'what' but the description does not cover the 'when' or 'why'.

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 descriptions cover 100% of the parameters, making the baseline 3. The description itself adds no parameter-specific meaning, but the schema already provides comprehensive documentation for each parameter.

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?

The description clearly states the tool finds latest files sorted by client-side modified timestamp, providing a specific verb and resource that distinguishes it from generic file search. However, it could be more explicit about the repository context, but that is covered in the schema.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives. Sibling tools like jfrog_find_files exist, and the description does not explain what makes this tool the better choice for latest-file scenarios.

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/mSaeedS/jfrog-mcp'

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