Skip to main content
Glama
shigechika

boxadm-mcp

by shigechika

external_collaborators

Scan Box folders to list collaborators outside your organization, including pending invites, so you can review external access.

Instructions

List external collaborators on Box folders (current state, enumeration).

Walks folders the authenticating co-admin user can see (default from the root "All Files") and reports collaborations whose collaborator is outside the org domain allowlist — accepted external users or pending external invites. Useful to review who outside the organization has standing access.

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 when coverage was cut short. max_depth: Folder recursion depth (default 1 = top-level folders only).

Externally-owned folders (this org is only a guest, not the owner) are out of scope and skipped — we cannot govern their collaborations, and their "external collaborators" are just the owner's own org accounts. They are reported separately under skipped_externally_owned (never silently dropped) and do not consume the max_folders budget.

Coverage note: limited to content the co-admin user can access (not provably 100% of the enterprise) and to the depth/folders caps. Returns folders_scanned, capped, fetch_errors (count of folders whose lookup hit an API error that outlasted the client's retries, e.g. a persistent 403 or a sustained throttle — coverage is complete only when capped is false AND fetch_errors is 0), count, external_collaborators (folder, owner, collaborator, role, status, expires_at), and skipped_externally_owned (folder_id, folder_name, owner). 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?

The description discloses extensive behavior: it refuses invalid root_folder_id with an error, skips externally-owned folders with separate reporting, and explains the max_folders cap via the `capped` field. Error handling for fetch errors is also detailed, covering persistent API errors and retries—all beyond what any annotation could provide.

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 front-loaded with a one-sentence summary, followed by structured details organized into coherent paragraphs. Each sentence contributes new information, such as coverage limitations and return fields, justifying its length.

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?

For a tool with no output schema and no annotations, the description provides a thorough account of return values, error behavior, and limitations (e.g., coverage only reflects co-admin's accessible folders). It covers all critical aspects an agent needs to invoke and interpret results correctly.

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?

Despite 0% schema description coverage, the Args section richly explains each parameter: root_folder_id's format and validation, max_folders' default and `capped` disclosure, and max_depth's recursion semantics. This fully compensates for the sparse 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 first line 'List external collaborators on Box folders (current state, enumeration)' uses a specific verb and resource, clearly distinguishing the tool's purpose. Though siblings like external_access_events exist, the description unambiguously defines what this tool does.

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?

Clear context is provided about walking folders from the root 'All Files' and the tool's usefulness for reviewing external standing access. However, no explicit alternatives or when-not-to-use conditions are given, aside from the out-of-scope externally-owned folders, which is more about tool behavior than usage guidance.

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