Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Project Folder

update_project_folder

Update an existing project folder's properties, such as name, parent folder, or tracking status, by specifying the folder ID and project ID.

Instructions

Update the specified folder. Use this to update an existing Documents (only the supplied fields are changed). Updates the specified Documents and returns the modified object on success. Required parameters: id, project_id. Procore API: Core > Documents. Endpoint: PATCH /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.
parent_idNoJSON request body field — the ID of the parent folder to move the folder to.
nameNoJSON request body field — the Name of the folder
is_trackedNoJSON request body field — status if a folder should be tracked (true/false)
explicit_permissionsNoJSON request body field — set folder to private (true/false)
custom_field_%{custom_field_definition_id}NoJSON request body field — value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ...
Behavior3/5

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

Annotations already indicate mutation (readOnlyHint=false) non-destructiveness. The description adds that only supplied fields are changed (partial update), but lacks details on auth needs, rate limits, or side effects.

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?

Relatively concise at 4 sentences. Front-loaded with main action, but includes redundant phrases and API endpoint info that may be extraneous for an agent.

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 the key aspects: partial update, return value, required parameters. No output schema exists, so description suffices. Could mention the folder-project association constraint.

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 coverage is 100% with clear descriptions. The description only repeats required parameters, adding no meaningful semantics beyond the 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?

The description clearly states the action ('Update') and resource ('folder'), but refers to 'Documents' ambiguously. It distinguishes this tool as project-specific via parameters, but doesn't explicitly differentiate from sibling tools like update_company_folder.

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?

No guidance on when to use this tool versus alternatives. Does not mention exclusions, prerequisites, or scenarios where other tools would be better suited.

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