Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Work Activity

update_work_activity

Update a work activity's name or active status for incident tracking. Modify specified fields to get the updated object.

Instructions

Updates a specified Work Activity. Note that Procore provided Work Activities' names cannot be changed. Use this to update an existing Incidents (only the supplied fields are changed). Updates the specified Incidents and returns the modified object on success. Required parameters: company_id, id, name. Procore API: Project Management > Incidents. Endpoint: PATCH /rest/v1.0/companies/{company_id}/incidents/work_activities/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — unique identifier of the Incidents resource
nameYesJSON request body field — the Name of the Work Activity
activeNoJSON request body field — flag that denotes if the Work Activity is available for use
Behavior3/5

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

Adds value beyond annotations by noting that Procore-provided names cannot be changed and that only supplied fields are updated. However, the 'Incidents' error detracts and no other behavioral traits are disclosed.

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?

Four sentences with some redundancy (two mentions of updating Incidents) and an error. Could be more concise by merging repeated info.

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 main behavior and constraints, but lacks explanation of the 'active' parameter (though schema covers it) and the reference to Incidents is misleading. No output schema reduces burden.

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?

All parameters have schema descriptions, so baseline is 3. The description only repeats required parameters without adding new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Updates a specified Work Activity,' but confusingly refers to 'Incidents' instead of 'Work Activities' in two places, which may cause ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus create, delete, or bulk_update_work_activities. The description only implies it is for updating existing entries.

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