Skip to main content
Glama

jfrog_find_files

Read-onlyIdempotent

Locate files in JFrog Artifactory by filtering on repository, name pattern, package type, and modification times. Return full item details or a summary with count and preview.

Instructions

Find files with generic filters and response shaping.

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.
cursorNoOpaque cursor returned by a previous response. Do not parse or construct cursor values client-side.
repo_keyNoOptional repository key to search. Required unless package_type is provided. Raw URLs, path separators, and control characters are rejected.
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.
summary_onlyNoReturn only counts and an items_preview instead of the full item list.
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 readOnlyHint, idempotentHint, and non-destructive behavior, so safety is covered. The description adds minimal behavioral context with 'response shaping,' but does not mention pagination via cursor, AQL pattern matching, or that results can be summarized—though these are discoverable in the schema.

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 sentence with no filler, making it maximally concise. It does not repeat schema details and earns its place by stating the tool's purpose in a straightforward manner.

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 that the schema documents all parameters, an output schema exists, and annotations cover the safety profile, the description is largely sufficient. However, the absence of usage guidance and the minimal overview of what 'generic filters' encompasses leaves some gaps for a tool with 11 parameters.

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?

The input schema has 100% description coverage across all 11 parameters, so the baseline is 3. The description's 'generic filters' provides a high-level hint but doesn't add parameter-specific meaning beyond what the schema already explains.

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 uses the verb 'Find' with the resource 'files' and specifies 'generic filters and response shaping', making the core function clear. It does not explicitly name sibling tools or contrast with them, so it falls short of full differentiation, but the phrase 'generic filters' suggests a flexible search capability.

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?

There is no guidance on when to use this tool instead of jfrog_list_path, jfrog_latest_files, or other siblings. The description only states what it does, not the appropriate context, exclusions, or alternatives.

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