Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Form

create_form

Create a new form for a Procore project by providing project ID, name, description, form template ID, and fillable PDF. Returns the created form with its new ID.

Instructions

Create a new Form associated with the specified Project. Pass the record's fields as top-level arguments — they are nested under "form" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted. Creates the form and returns it with its new id (HTTP 201); calling it again creates another record. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. 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
nameYesJSON request body field — the Name of the Form
privateNoJSON request body field — the Private status of the Form
project_idYesURL path parameter — unique identifier for the project.
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.
descriptionYesJSON request body field — the Description 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.
form_template_idYesJSON request body field — iD of the Form Template that the Form is made from
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it returns the new ID with HTTP 201, it is non-idempotent (mirroring idempotentHint=false but adding specifics), it explains payload nesting, and it details common error statuses (401, 403, 404). This gives the agent a clear mental model of the tool's behavior without contradicting any annotations.

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?

The description is a single dense paragraph covering multiple key points: action, payload handling, default behavior, idempotency, error handling, required parameters, and API reference. While not overly verbose, it could be structured with bullet points for improved readability. Every sentence serves a purpose, so it earns a 4.

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

Completeness5/5

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

For a create operation with 7 parameters and no output schema, the description is remarkably complete. It explains the response (new ID, HTTP 201), non-idempotency, error handling, payload nesting, default project_id, required parameters, and the exact endpoint. This is sufficient for an agent to understand and invoke the tool correctly without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying that parameters are passed as top-level arguments and are automatically nested under 'form' in the payload, and that project_id defaults from config. It also lists required parameters, reinforcing the schema. This extra context raises the score above baseline.

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's action: 'Create a new Form associated with the specified Project.' This uses a specific verb and resource, and distinguishes itself from sibling tools like update_form and show_form by explicitly focusing on creation. It also specifies the endpoint, making the purpose unambiguous.

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 provides clear usage context: it creates a new form, notes that project_id defaults to the configured value when omitted, and explicitly states non-idempotency ('calling it again creates another record'). However, it does not explicitly mention when to use this tool over alternatives or provide exclusion criteria, so it stops short of a 5.

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