Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update A Single Group

update_a_single_group

Update a group's information such as name, timezone, address, and contact details using its unique ID. This modifies the group record in the Resource Planning module.

Instructions

Update the single Group in a given ID and body. Use this to perform the update a action on Resource Planning records. Creates a new Resource Planning records and returns the created object on success (HTTP 201). Required parameters: company_id, group_id, name, timezone. Procore API: Resource Management > Resource Planning. Endpoint: POST /rest/v1.0/workforce-planning/v2/companies/{company_id}/groups/{group_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company. This parameter accepts both formats: - **Recommended**: Procore company ID (integer) - Use this for new integrations - Legacy: LaborChart UUID format (uuid string...
group_idYesURL path parameter — unique identifier for the group
nameYesJSON request body field — group Name.
timezoneYesJSON request body field — the default Timezone for scheduling outbound messages from projects in this group that don't specify their own Timezone. Example format: America/Chicago.
colorNoJSON request body field — hexadecimal color code for the Group. Can be helpful for categorization. Example: #53A9FF.
address_1NoJSON request body field — the first part of the Group's address.
address_2NoJSON request body field — the second part of the Group's address (e.g., Apartment, Suite, Unit).
city_townNoJSON request body field — the City or Town for the Group.
state_provinceNoJSON request body field — the State or Province for the Group.
zipcodeNoJSON request body field — zip or Postal Code for the Group.
countryNoJSON request body field — the Country for the Group.
contact_nameNoJSON request body field — the Point of Contact (P.O.C.) name for the Group.
contact_phoneNoJSON request body field — phone number for the Group's Point of Contact. Must include country and area code.
contact_emailNoJSON request body field — email address for the Group's Point of Contact.
Behavior1/5

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

The description contains an internal contradiction (update vs. create) and does not disclose behavioral traits beyond basic action. Annotations are present but the description's inconsistency undermines trust. No mention of permissions, side effects, or idempotency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a run-on sentence that includes conflicting information (update vs. create) and extraneous details like HTTP status code and endpoint path. It is not concise and wastes space with incorrect statements.

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

Completeness2/5

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

No output schema exists, so the description should at minimum clarify return values. It mentions 'returns the created object' but contradicts the update nature. Missing critical info like authentication requirements, idempotency, and specific parameter constraints.

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?

The input schema covers 100% of parameters with detailed descriptions. The tool's description lists required parameters but adds no additional meaning beyond what the schema already provides. Baseline of 3 is appropriate.

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

Purpose1/5

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

The description states both 'Update the single Group' and 'Creates a new Resource Planning records', which is contradictory and confusing. The tool name indicates an update, but the description implies creation, severely undermining purpose clarity.

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 is provided on when to use this tool versus alternatives. Among many sibling update tools, there is no differentiation or usage context.

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