Skip to main content
Glama
shigechika

boxadm-mcp

by shigechika

external_collaborators

Enumerate external collaborators on Box folders by scanning accessible folders and reporting collaborations with users outside the organization domain allowlist. Identify external access risks.

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). 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).

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, count, and external_collaborators (folder, owner, collaborator, role, status, expires_at). On failure returns {"error": ...}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_depthNo
max_foldersNo
root_folder_idNo0
Behavior5/5

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

With no annotations, the description compensates thoroughly: it discloses folder walking from root, limits via max_folders and max_depth, coverage limitations (co-admin access), capped behavior, and return fields including error case. This fully informs behavior beyond 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 well-structured with a front-loaded purpose sentence, followed by detailed but concise parameter explanations and a coverage note. Every sentence adds value, and the length is appropriate for the complexity.

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?

Despite no output schema, the description specifies all return fields (folders_scanned, capped, count, external_collaborators with subfields) and error handling. The complexity (recursion, caps, access limits) is fully covered, making it complete for agent invocation.

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%, but the description provides explicit meanings for all three parameters: root_folder_id as '0' for user's root, max_folders with default 150 and capped disclosure, max_depth with default 1. This compensates fully for the missing schema descriptions.

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 clearly states the verb 'List' and the resource 'external collaborators on Box folders', and distinguishes from sibling tools like 'external_access_events' and 'top_external_sharers' by focusing on current state enumeration via folder walking.

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 explicitly states it is 'Useful to review who outside the organization has standing access', providing a clear use case. However, it does not discuss when not to use or compare with sibling tools, so it lacks explicit 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/shigechika/boxadm-mcp'

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