Skip to main content
Glama
shigechika

boxadm-mcp

by shigechika

public_shared_links

Scan Box folders to list files and folders whose shared links are open to anyone with the URL, identifying exposed sharing risks.

Instructions

List items with an open ("anyone with the link") shared link (enumeration).

Walks folders the authenticating co-admin user can see and reports files and folders whose shared link access is open — reachable by anyone with the URL, the highest-exposure sharing mode.

Args: root_folder_id: Folder to start from ("0" = the user's root). A Box folder id: decimal digits only, as shown at the end of a Box folder URL. Anything else is refused with {"error": ...} before any request is made, rather than being reported as an empty result. max_folders: Cap on folders visited (default 150); capped discloses truncation. max_depth: Folder recursion depth (default 1 = top-level only; raise to reach file links inside folders).

Coverage note: limited to content the co-admin user can access and to the caps. Returns folders_scanned, capped, fetch_errors (count of folders whose lookup hit an API error; coverage is complete only when capped is false AND fetch_errors is 0), count, and public_shared_links (item type/id/name, owner, access, can_download). On failure returns {"error": ...}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_depthNo
max_foldersNo
root_folder_idNo0

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so excellently. It discloses traversal behavior, access limitations, caps, error handling for invalid root_folder_id, fetch_errors count, and exact conditions under which coverage is complete. This far exceeds minimal expectations.

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 well-structured with an opening summary, per-argument explanations, and a coverage/output note. Despite its length, every sentence adds necessary operational or behavioral detail, and the formatting aids readability.

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

Completeness5/5

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

Given no output schema and a moderately complex traversal tool, the description is complete. It enumerates all returned fields, explains their semantics, covers failure modes, and specifies scope boundaries. An agent has enough information to predict behavior and handle edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully compensate. It explains all three parameters in depth: root_folder_id format and validation failure behavior, max_folders default and truncation disclosure, and max_depth default with recursion guidance. This adds significant meaning beyond the raw schema.

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 opens with a specific verb and resource: "List items with an open ('anyone with the link') shared link." It clearly defines the tool's scope (enumeration of open shared links) and differentiates it from sibling tools focused on events, collaborators, or sharers.

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

Usage Guidelines4/5

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

The description provides clear usage context: it walks folders the authenticating co-admin user can see, starts from a specified root folder, and enumerates only open shared links. It does not explicitly name alternatives or state when not to use this tool, but the context is precise enough for an agent to decide.

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

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/shigechika/boxadm-mcp'

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