Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Company Form Template

update_company_form_template
Idempotent

Update an existing Procore company form template by sending only changed fields; omitted fields remain unchanged. Provide id and company_id to modify name, description, or fillable PDF.

Instructions

Updates an existing company form template for the specified Procore company. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "form_template" in the request payload for you. company_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified company form template on success. 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: id, company_id. Procore API: Project Management > Forms. Endpoint: PATCH /rest/v1.0/companies/{company_id}/form_templates/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — company Form Template ID
nameNoJSON request body field — the Name of the Form Template
company_idYesURL path parameter — unique identifier for the company.
descriptionNoJSON request body field — the Description of the Form Template
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.
Behavior5/5

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

The description reveals partial-update semantics (omitted fields keep current values), the payload nesting convention, company_id defaulting from procore_set_config, and specific error conditions (401/403/404). These are not present in the annotations and meaningfully inform the agent about side effects and failure modes.

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 longer than average but every sentence carries operational value, from update semantics to error handling. It is front-loaded with the purpose and ends with API context, maintaining a logical flow without padding.

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?

The description covers purpose, update behavior, parameter nuances, expected return value, and common failure responses, compensating for the lack of an output schema. Given the tool's moderate complexity, this is thorough and leaves little ambiguity.

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 a baseline of 3 applies. The description adds value by explaining that fields are optional for partial updates, that company_id defaults to the configured value, and that id must reference an existing record found via a list tool—details beyond the schema's field descriptions.

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 opens with a specific verb and resource: 'Updates an existing company form template for the specified Procore company,' clearly distinguishing this update operation from sibling tools like create_company_form_template or delete_company_form_template. It also specifies the HTTP method and endpoint, reinforcing the tool's exact role.

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?

It states that this tool updates an existing template and instructs to resolve the id with the matching list tool first, providing a concrete prerequisite. It implies use for modifications rather than creation/deletion, but doesn't explicitly list when to prefer alternatives.

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