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 using its ID and project ID. Returns a JSON object with folder details including children and file versions.

Instructions

Show detail on the specified folder. Must be either true or false. Use this to fetch the full details of a specific Documents by its identifier. Returns a JSON object describing the requested Documents. 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_foldersNoQuery string parameter — exclude children Folders from results. Must be either true or false.
exclude_filesNoQuery string parameter — exclude children files 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.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds only that it returns a JSON object, which is obvious. It does not disclose additional behavioral traits like pagination behavior or auth requirements.

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

Conciseness3/5

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

Description is moderately concise but includes an irrelevant sentence ('Must be either true or false') that disrupts clarity. It could be restructured to front-load the primary action and remove extraneous content.

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?

With 7 parameters and no output schema, the description fails to explain optional parameters like exclude_folders, exclude_files, show_latest_file_version_only, and pagination. The note about 'Must be either true or false' adds confusion rather than completeness.

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

Parameters3/5

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

Schema covers 100% of parameters with descriptions. The description repeats required parameters (id, project_id) and includes the ambiguous 'Must be either true or false' which may mislead. Adds minimal value beyond schema.

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?

Clearly states it shows details of a specified folder, but the phrase 'Must be either true or false' is confusing and appears out of place. It differentiates from sibling tools by mentioning 'folder' and 'Documents'.

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

Usage Guidelines3/5

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

Says 'Use this to fetch the full details of a specific Documents by its identifier', implying when to use. However, it does not explicitly state when not to use or mention alternative tools among the many sibling tools.

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