Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Resource

update_resource_project

Update an existing Schedule (Legacy) resource in a Procore project. Only supplied fields are changed using project ID, resource ID, and resource object.

Instructions

Update the specified Resource. Use this to update an existing Schedule (Legacy) records (only the supplied fields are changed). Updates the specified Schedule (Legacy) records and returns the modified object on success. Required parameters: project_id, id, project_id, resource. Procore API (v1.1): Project Management > Schedule (Legacy). Endpoint: PATCH /rest/v1.1/projects/{project_id}/schedule/resources/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesJSON request body field — the ID of the Project the Resource belongs to
idYesURL path parameter — unique identifier of the Schedule (Legacy) resource
resourceYesJSON request body field — resource object
Behavior4/5

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

Description discloses that only supplied fields are changed and returns the modified object. Annotations confirm non-destructive, no contradiction. Could mention error behavior but not required.

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?

Description has 3 sentences, but the third is long and includes a duplicate 'project_id' typo. Could be more concise. Adequate but not polished.

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, description explains return value. Provides endpoint and API version. Missing error scenarios, but overall sufficient for an update operation.

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%, so baseline 3. Description adds minimal value beyond listing required parameters, which is redundant. No additional semantics for the resource object.

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 it updates a resource, specifies it operates on Schedule (Legacy) records, and distinguishes from sibling tools like create/delete. The verb 'update' and resource are explicit.

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 says to use for updating existing Schedule (Legacy) records and mentions partial update. It does not explicitly list alternatives or when not to use, but context with siblings is clear.

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