Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A Single Group

create_a_single_group

Create a new Resource Planning group in Procore by providing company ID, name, and timezone. Returns the created group object.

Instructions

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

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...
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.
Behavior4/5

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

Annotations already indicate not read-only and not destructive. The description adds that it creates and returns the created object on HTTP 201, which is consistent. No additional behavioral traits like permissions or side effects are disclosed, but it's adequate for a straightforward creation tool.

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

Conciseness5/5

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

The description is extremely concise, front-loading the purpose in the first sentence, listing required parameters, and providing API context in a single additional sentence. No redundant information.

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?

Given no output schema, the description mentions the return value ('returns the created object on success'). It covers the required parameters and the API endpoint. It could mention that other parameters are optional, but overall it is sufficient for a simple create tool.

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?

Schema coverage is 100% with detailed parameter descriptions. The description only lists required parameters, adding no extra meaning beyond what the schema provides. Baseline 3 is appropriate as description does not compensate for 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 'Create' and the resource 'Single Group', specifies it's for Resource Planning records in Procore, and distinguishes it from sibling tools like update_a_single_group and delete_a_single_group by its creation purpose.

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 explicitly says 'Use this to create a new Resource Planning records', provides required parameters, and the context of siblings makes when to use vs. alternatives clear. However, it lacks explicit 'when not to use' 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