Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Instruction

update_instruction

Update an existing instruction in a Procore project. Modify fields like title, status, description, and attachments.

Instructions

Update the specified Instruction. Use this to update an existing Daily Log records (only the supplied fields are changed). Updates the specified Daily Log records and returns the modified object on success. Required parameters: project_id, id. Procore API: Project Management > Daily Log. Endpoint: PATCH /rest/v1.0/projects/{project_id}/instructions/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Daily Log resource
send_emailsNoQuery string parameter — designates whether or not emails will be sent (default false)
numberNoJSON request body field — the Number of the Instruction
titleNoJSON request body field — the Title of the Instruction
statusNoJSON request body field — the Status of the Instruction
instruction_type_idNoJSON request body field — iD of the Instruction Type
instruction_from_idNoJSON request body field — iD of the User who the Instruction is from
date_receivedNoJSON request body field — the date received for this Daily Log operation
schedule_impactNoJSON request body field — the Schedule Impact of the Instruction
cost_impactNoJSON request body field — the Cost Impact of the Instruction
privateNoJSON request body field — the Private status of the Instruction
descriptionNoJSON request body field — the Description of the Instruction
attention_idsNoJSON request body field — an array of IDs of the Attentions of the Instruction
distribution_member_idsNoJSON request body field — an array of IDs of the Distributions of the Instruction
trade_idsNoJSON request body field — an array of IDs of the Trades of the Instruction
attachmentsNoJSON request body field — instruction's Attachments. To upload attachments you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with `attachments[]` as fi...
upload_idsNoJSON request body field — the specified array of upload ids is saved as Site Instruction Attachments.
Behavior3/5

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

Annotations already indicate write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that only supplied fields are changed (PATCH behavior) and that the modified object is returned. It does not disclose authentication needs, rate limits, or other side effects beyond what annotations provide.

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

Conciseness4/5

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

The description is concise, with 4 sentences front-loading the purpose. It includes usage, return value, required params, and API context without unnecessary repetition. Slightly redundant with schema but overall efficient.

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?

Given the tool's 18 parameters including nested objects and attachments requiring multipart/form-data, the description is minimal. It does not explain return structure (no output schema), guide parameter combinations, or highlight the multipart requirement beyond schema. Adequate but not exhaustive.

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 covers 100% of parameters with descriptions. The description only reiterates the required parameters (project_id, id) and notes 'only the supplied fields are changed,' but provides no additional per-parameter semantics 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.

Purpose5/5

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

The description explicitly states 'Update the specified Instruction' with a clear verb and resource, and distinguishes from sibling tools like create_instruction, delete_instruction, and update_instruction_type by specifying it updates existing Daily Log records (instructions). The endpoint and required parameters further clarify the scope.

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 provides usage context: 'Use this to update an existing Daily Log records (only the supplied fields are changed).' This implies partial updates and when to use it. It does not explicitly exclude creation or deletion, but the verb 'update' and the mention of 'existing' make it clear. No explicit alternatives are named, but the context is sufficient.

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