Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Form

create_form

Create a new form in a Procore project by providing project ID, name, description, form template ID, and fillable PDF.

Instructions

Create a new Form associated with the specified Project. Use this to create a new Forms in Procore. Creates a new Forms and returns the created object on success (HTTP 201). Required parameters: project_id, name, description, form_template_id, fillable_pdf. Procore API: Project Management > Forms. Endpoint: POST /rest/v1.0/projects/{project_id}/forms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
nameYesJSON request body field — the Name of the Form
descriptionYesJSON request body field — the Description of the Form
form_template_idYesJSON request body field — iD of the Form Template that the Form is made from
privateNoJSON request body field — the Private status of the Form
fillable_pdfYesJSON 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.
Behavior3/5

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

Annotations already indicate it's a non-read, non-destructive, non-idempotent operation. The description adds that it returns the created object on success (HTTP 201), which is valuable. However, it does not disclose error handling, idempotency implications, or side effects beyond creation.

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?

Three sentences with some redundancy (e.g., 'Create a new Form... Use this to create a new Forms... Creates a new Forms...'). It is front-loaded with purpose but could be more concise by removing repetitive phrasing.

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?

Covers the endpoint, required parameters, and HTTP response status. However, with no output schema, it does not describe the structure of the returned object. Optional parameters (private, attachments) are not mentioned in the description, leaving some gaps in 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?

Input schema has 100% description coverage, so baseline is 3. The description lists required parameters but does not add meaning beyond the schema for those parameters. It repeats the multipart/form-data requirement already in the schema, offering no additional insight.

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 the verb 'Create' and resource 'Form' associated with a Project. The description specifies the action, resource, and scope (project-level), and distinguishes from other form-related tools like 'delete_form' by focusing on creation.

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?

Provides basic context that this tool is for creating new Forms in Procore and lists required parameters. However, it lacks guidance on when not to use it (e.g., for updating forms) or alternatives like 'create_company_form_template'. No explicit when-to-use or exclusions.

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