Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Company Folder

show_company_folder
Read-onlyIdempotent

Retrieve detailed information about a specific folder in Procore Documents. Uses company and folder IDs to return folder properties, with optional pagination for child items.

Instructions

Show detail on a specific Folder. Use this to fetch the full details of a specific Documents by its identifier. Returns a JSON object describing the requested Documents. Required parameters: company_id, id. Procore API: Core > Documents. Endpoint: GET /rest/v1.0/companies/{company_id}/folders/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — unique identifier of the Documents resource
exclude_foldersNoQuery string parameter — exclude children Folders from results
exclude_filesNoQuery string parameter — exclude children Files from results
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that it returns a JSON object, but does not disclose the structure or pagination behavior. It does not contradict annotations.

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?

The description is four sentences but contains some redundancy (e.g., 'Show detail on a specific Folder' and 'fetch the full details of a specific Documents'). The API endpoint info is useful but could be more tightly worded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 parameters and no output schema, the description provides a basic purpose but omits details on optional parameters (exclude_folders, exclude_files, pagination) and the response structure. Annotations cover safety, but overall completeness is adequate.

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 descriptions cover all 6 parameters with 100% coverage. The description only mentions the required parameters (company_id, id), adding no new meaning. Baseline 3 is appropriate since schema handles semantics.

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 detail on a specific Folder, distinguishing it from listing tools. However, it inconsistently refers to 'Documents' instead of 'Folder' in the second sentence, which slightly undermines clarity.

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 implies usage for fetching details by identifier but provides no explicit guidance on when to use this tool versus alternatives like listing tools or other show tools. No when-not or alternative tools are mentioned.

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