Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Asset

create_asset_company

Create a company asset in Procore using company, asset type, and status IDs. Returns the created asset with its new ID.

Instructions

Creates a new company asset with the provided details. company_id defaults to the value set by procore_set_config when omitted. Creates the asset 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: company_id, asset_type_id, asset_status_id. Procore API (v2.0): Core > Assets. Endpoint: POST /rest/v2.0/companies/{company_id}/assets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeNoJSON request body field — latitude must be provided together with longitude, or both must be omitted.(only applicable for project asset)
trade_idNoJSON request body field — trade ID associated with the asset
longitudeNoJSON request body field — longitude must be provided together with latitude, or both must be omitted.(only applicable for project asset)
asset_codeNoJSON request body field — unique identifier for the asset (also referred to as asset_code in API). Must be unique at company level (case-insensitive). Optional when an active naming rule exists—the ID (code) will be auto-ge...
asset_nameNoJSON request body field — name of the asset.
company_idYesURL path parameter — unique identifier for the company.
descriptionNoJSON request body field — description of the asset
location_idNoJSON request body field — location ID where the asset is located (only applicable for project asset)
asset_type_idYesJSON request body field — asset type ID (primary key of the asset type). Must have Is Asset enabled for that type.
custom_fieldsNoJSON request body field — custom fields map. Key: 'custom\_field\_{id}'. Supported types: STRING (text), RICH_TEXT (HTML), BOOLEAN, DECIMAL, DATETIME (ISO 8601), LOV_ENTRY ({id, name}), LOV_ENTRIES ([{id, name}]). Field def...
Accept-LanguageNoJSON request body field — locale for localized response messages (for example: en, fr-FR, pseudo)
asset_status_idYesJSON request body field — unique identifier of the asset status
parent_asset_idNoJSON request body field — parent asset ID. Optional. When provided, creates a parent-child relationship. The parent must exist, belong to the same company, and be in the same asset type hierarchy.
profile_image_idNoJSON request body field — profile image FAS ID
Behavior5/5

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

Annotations already indicate non-idempotency, but the description reinforces it with 'calling it again creates another record' and adds valuable context: success returns HTTP 201 with new id, failures return an error payload, and common statuses (401, 403, 404) are explained. This goes well beyond what annotations provide.

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 front-loaded with the core purpose and contains logically ordered details (default behavior, response, error handling, requirements, API reference). It is slightly verbose but every sentence contributes useful information, so it earns a 4.

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 the essential behavioral aspects: creation, response (new id, HTTP 201), non-idempotency, error payload structure, common status codes, required parameters, and API endpoint. Given the tool's complexity (14 parameters, no output schema), this is reasonably complete, though it stops short of detailing the full return object.

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 description coverage is 100%, so baseline is 3. The description adds meaningful context by explaining that company_id defaults to the value set by procore_set_config when omitted, and it explicitly lists the required parameters. This extra information enhances understanding beyond the 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?

The description clearly states the verb and resource: 'Creates a new company asset.' It specifies the company scope and includes the API endpoint, distinguishing it from project-level asset tools like create_asset_project via the 'company asset' phrasing and company_id requirement.

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?

The description implies usage for creating company-level assets and notes that company_id defaults to procore_set_config, but it does not explicitly state when to use this tool over alternatives or provide exclusions. This is adequate but lacks direct alternative guidance.

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