Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Project Folder

show_project_folder
Read-onlyIdempotent

Retrieve detailed information about a specific project folder in Procore, including its files and subfolders. Requires the folder ID and project ID.

Instructions

Show detail on the specified folder. Must be either true or false. Use this when you already know which project folder you want and need its full field set. id must identify an existing parent record — resolve it with the matching list tool first. Returns a single JSON object describing the project folder. Read-only — it changes nothing in Procore. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: id, project_id. Procore API: Core > Documents. Endpoint: GET /rest/v1.0/folders/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Documents resource
project_idYesQuery string parameter — unique identifier for the project.
exclude_filesNoQuery string parameter — exclude children files from results. Must be either true or false.
exclude_foldersNoQuery string parameter — exclude children Folders from results. Must be either true or false.
show_latest_file_version_onlyNoQuery string parameter — show only the latest file version. Must be either true or false.
Behavior4/5

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

Annotations already declare the tool read-only and non-destructive; the description reinforces this by stating it changes nothing in Procore. It also adds useful failure details (401/403/404). No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description contains useful context (endpoint, error statuses, read-only clarification) but includes an orphaned sentence 'Must be either true or false' that lacks referent and slightly harms clarity. Otherwise it is tightly written.

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?

Covers purpose, usage trigger, prerequisite resolution, return value, read-only behavior, and common failure modes. No output schema, so the return description is sufficient. Minor gap: does not explicitly contrast with company-scoped sibling tools, but the name and description make the project scope clear.

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

Parameters4/5

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

Schema coverage is 100%, so parameters are already documented. The description adds valuable semantic guidance for the id parameter (must exist, resolve via list tool first). The stray phrase 'Must be either true or false' is confusing but does not undermine the parameter guidance.

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 tool shows detail on a specified project folder and returns a single JSON object with the full field set. This distinguishes it from listing tools and sibling scoped variants.

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?

It explicitly says to use this tool when you already know which project folder you need, and instructs resolving the id with the matching list tool first. It does not name the exact sibling list tool but provides clear 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/TylerIlunga/procore-mcp-server'

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