Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Instruction

update_instruction
Idempotent

Update an existing Procore Daily Log instruction by sending only changed fields; specify project and instruction IDs. Returns the updated instruction or error details.

Instructions

Update the specified Instruction. Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "instruction" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified instruction on success. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. 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
idYesURL path parameter — unique identifier of the Daily Log resource
titleNoJSON request body field — the Title of the Instruction
numberNoJSON request body field — the Number of the Instruction
statusNoJSON request body field — the Status of the Instruction
privateNoJSON request body field — the Private status of the Instruction
trade_idsNoJSON request body field — an array of IDs of the Trades of the Instruction
project_idYesURL path parameter — unique identifier for the project.
upload_idsNoJSON request body field — the specified array of upload ids is saved as Site Instruction Attachments.
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...
cost_impactNoJSON request body field — the Cost Impact of the Instruction
descriptionNoJSON request body field — the Description of the Instruction
send_emailsNoQuery string parameter — designates whether or not emails will be sent (default false)
attention_idsNoJSON request body field — an array of IDs of the Attentions of the Instruction
date_receivedNoJSON request body field — the date received for this Daily Log operation
schedule_impactNoJSON request body field — the Schedule Impact of the Instruction
instruction_from_idNoJSON request body field — iD of the User who the Instruction is from
instruction_type_idNoJSON request body field — iD of the Instruction Type
distribution_member_idsNoJSON request body field — an array of IDs of the Distributions of the Instruction
Behavior5/5

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

The description discloses partial-update behavior, project_id default, error payload structure with common HTTP status codes, and the fact that fields are nested under 'instruction' in the request payload. These details go well beyond the annotations (readOnlyHint false, destructiveHint false) and provide valuable context for the agent.

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 and front-loaded with the action, followed by usage details, defaults, error handling, and endpoint. Each sentence adds value; the 'Required parameters' sentence duplicates schema but is not wasteful. Structure is logical and scannable.

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 18 parameters, a nested payload, and no output schema, the description covers key behaviors: update semantics, return value, error scenarios, and id resolution. It doesn't describe the output structure in detail, but the return is specified as the modified instruction. It omits the multipart/form-data requirement for attachments, but that is covered in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics: 'Send only fields you intend to change' clarifies optional parameters, 'project_id defaults...' and 'id must identify existing parent record' provide crucial context beyond the schema. It also explains top-level argument nesting.

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 'Update the specified Instruction' with a specific verb and resource. It also provides the endpoint and required parameters, making it distinct from sibling tools like create_instructions, show_instruction, and delete_instruction.

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?

It gives clear usage guidance: 'Send only the fields you intend to change' and instructs to resolve the id with the matching list tool first. It also mentions the project_id default from procore_set_config. However, it does not explicitly say when not to use this tool (e.g., for creating new instructions), though that is implied by 'Update' and the existing id requirement.

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