Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Project File

update_project_file

Update a Procore project file (creates a new version). Modify name, folder, description, permissions, or upload a new file. Requires file ID and project ID.

Instructions

Update the specified File (creates a new file version). 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/files/{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 file to
nameNoJSON request body field — the Name of the file
checked_out_untilNoJSON request body field — check out a file until the specified time. Admins may reset checkout by sending "null"
is_trackedNoJSON request body field — status if a file should be tracked (true/false)
explicit_permissionsNoJSON request body field — set file to private (true/false)
descriptionNoJSON request body field — a description of the file
dataNoJSON request body field — [DEPRECATED] File to use as file data. Please use upload_uuid instead. Note that it's only possible to post a file using a multipart/form-data body (see RFC 2388). Most HTTP libraries will do the r...
upload_uuidNoJSON request body field — uUID referencing a previously completed Upload. This is the recommended approach for file uploads. See Company Uploads or Project Uploads endpoints for instructions on how to use uploads. You sho...
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 ...
Behavior4/5

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

Disclosures beyond annotations: 'creates a new file version' and 'returns the modified object on success'. Annotations only state non-readonly and non-destructive; description adds versioning and response behavior.

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?

Four sentences covering action, usage, required fields, and API context. No wasted words; front-loaded with key information.

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?

Explains return value and references Procore API details. Lacks error conditions or prerequisites, but overall adequate for a mutation tool with many parameters and no output schema.

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%, so parameters are well-documented. The description only reiterates required parameters and the 'only supplied fields are changed' concept, adding minimal value beyond schema.

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?

Clearly states it updates a file by creating a new version, explicitly lists required parameters, and distinguishes the action from other operations. The verb 'Update' and resource 'File' are specific and align with the tool name.

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?

Provides clear context: 'Use this to update an existing Documents (only the supplied fields are changed).' It tells when to use but does not explicitly exclude scenarios or mention alternatives among 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