Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Form

update_form

Update an existing form in Procore by providing project and form IDs. Modify name, description, attachments, or other fields as needed.

Instructions

Update the specified Form. Use this to update an existing Forms (only the supplied fields are changed). Updates the specified Forms and returns the modified object on success. Required parameters: project_id, id. Procore API: Project Management > Forms. Endpoint: PATCH /rest/v1.0/projects/{project_id}/forms/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Forms resource
send_emailsNoQuery string parameter — designates whether or not emails will be sent (default false)
nameNoJSON request body field — the Name of the Form
descriptionNoJSON request body field — the Description of the Form
privateNoJSON request body field — the Private status of the Form
fillable_pdfNoJSON request body field — form's Fillable PDF. To upload a fillable PDF you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `fillable_pdf` as files.
attachmentsNoJSON request body field — form's Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as files.
Behavior4/5

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

Beyond annotations, the description reveals partial update behavior ('only the supplied fields are changed') and that it returns the modified object. This adds useful context that annotations do not provide.

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?

Three sentences efficiently convey purpose, usage, required parameters, and API reference. Every sentence adds value with no redundancy.

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?

The description covers essential information: purpose, partial update, required parameters, and return value. The multipart/form-data requirement is handled by the schema. Given no output schema, the description is mostly complete.

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 detailed parameter descriptions. The tool description only highlights required parameters (project_id, id) but adds no extra meaning beyond the schema. Baseline 3 is appropriate.

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 updates an existing Form and specifies the verb 'Update' and resource 'Form'. It is unambiguous and distinguishes from siblings like create_form and delete_form.

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?

The description says 'Use this to update an existing Forms (only the supplied fields are changed)' providing clear when-to-use context. However, it does not explicitly mention when not to use or list alternatives, but the purpose is straightforward.

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