Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update A Single Resource Request

update_a_single_resource_request

Update an existing resource request by specifying only the fields to change. Provide company ID and request ID to modify details like dates, allocation, or job title.

Instructions

Updates an existing Resource Request within a company. Only specified properties in the request body will be updated. 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, request_id. Procore API: Resource Management > Resource Planning. Endpoint: POST /rest/v1.0/workforce-planning/v2/companies/{company_id}/resource-requests/{request_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...
request_idYesURL path parameter — unique identifier for the Resource Request.
start_dayNoJSON request body field — the first day the requested resource is needed (ISO 8601).
end_dayNoJSON request body field — the last day the requested resource is needed (ISO 8601).
start_timeNoJSON request body field — start time of the request (HH:MM am/pm format).
end_timeNoJSON request body field — end time of the request (HH:MM am/pm format).
percent_allocatedNoJSON request body field — allocation percentage if the request is not hour-based.
job_title_idNoJSON request body field — job Title UUID for this request.
category_idNoJSON request body field — uUID of the Project Category.
subcategory_idNoJSON request body field — uUID of the Project Subcategory.
state_idNoJSON request body field — uUID of the Assignment State.
work_scope_textNoJSON request body field — scope of Work for the Resource Request.
instruction_textNoJSON request body field — instructions for the Resource Request.
work_daysNoJSON request body field — object to control working days (Sunday - Saturday as 0-6 index).
Behavior2/5

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

Annotations are minimal (no readOnly, destructive, idempotent hints). Description adds that only specified properties are updated, but contradicts itself with creation language. No disclosure of side effects, authentication, or rate limits.

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?

Relatively short but includes contradictory creation statement and redundant phrasing. Could be more concise and clear.

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?

With 14 parameters, nested objects, and no output schema, the description is incomplete. It doesn't explain return value (misleadingly says HTTP 201 for creation), error states, or differentiate from sibling tools.

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?

Input schema has full descriptions (100% coverage). Description only mentions required parameters company_id and request_id, adding little beyond the schema. Baseline 3 is appropriate.

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

Purpose3/5

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

The description states it updates an existing Resource Request, but then contradicts itself by mentioning 'Creates a new Resource Planning records' and HTTP 201 (creation). This ambiguity reduces 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 explicit guidance on when to use this tool versus alternatives like create or delete. Simply says 'Use this to perform the update a action' without differentiating from siblings.

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