Skip to main content
Glama

get-folder-contents

List files and subfolders in Autodesk Construction Cloud projects or specific directories to manage project documentation and assets.

Instructions

List contents of a project or a specific subfolder in Autodesk Construction Cloud

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYes
projectIdYes
folderIdNo

Implementation Reference

  • The async callback handler that performs authentication, initializes the DataManagementClient, fetches folder contents or project top folders, and returns formatted content.
    callback: async ({ accountId, projectId, folderId }) => {
        // TODO: add pagination support
        const accessToken = await getAccessToken(["data:read"]);
        const dataManagementClient = new DataManagementClient();
        const contents = folderId
            ? await dataManagementClient.getFolderContents(projectId, folderId, { accessToken })
            : await dataManagementClient.getProjectTopFolders(accountId, projectId, { accessToken });
        if (!contents.data) {
            throw new Error("No contents found");
        }
        return {
            content: contents.data.map((item) => ({ type: "text", text: JSON.stringify(item) }))
        };
    }
  • Input schema defining parameters: accountId (required string), projectId (required string), folderId (optional string).
    const schema = {
        accountId: z.string().nonempty(),
        projectId: z.string().nonempty(),
        folderId: z.string().optional()
    };
  • src/server.ts:12-14 (registration)
    Generic registration loop that adds all tools exported from src/tools/index.ts to the MCP server, including 'get-folder-contents' via its title.
    for (const tool of Object.values(tools)) {
        server.tool(tool.title, tool.description, tool.schema, tool.callback);
    }
  • src/tools/index.ts:3-3 (registration)
    Re-exports the getFolderContents tool from its implementation file for bulk import in server.ts.
    export { getFolderContents } from "./get-folder-contents.js";
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It implies a read-only operation ('List contents'), but doesn't specify whether it's paginated, what format the contents are returned in, or any rate limits or authentication requirements, which are critical for a tool with multiple required parameters.

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, efficient sentence that front-loads the core purpose without unnecessary words. Every part of it contributes directly to understanding the tool's function, making it highly concise and well-structured.

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?

Given the complexity (3 parameters, 2 required, no output schema, and no annotations), the description is inadequate. It doesn't explain the return values, error conditions, or how parameters interact (e.g., that 'folderId' is optional for listing root contents), leaving significant gaps for the agent to operate effectively.

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

Parameters2/5

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

The schema description coverage is 0%, so the description must compensate but fails to do so. It mentions 'project or a specific subfolder' which hints at the use of 'projectId' and optional 'folderId', but doesn't explain what 'accountId' is for, the relationships between parameters, or any constraints beyond what the schema minimally defines (like string types).

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 action ('List contents') and resource ('project or a specific subfolder in Autodesk Construction Cloud'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential siblings that might also list contents in different contexts or with different scopes, which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing account and project IDs), exclusions, or how it relates to sibling tools like 'get-projects' or 'get-item-versions', leaving the agent to infer usage context.

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/petrbroz/aps-mcp-server'

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