Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Instructions

create_instructions

Create a new instruction for a project's daily log in Procore, requiring project ID, title, status, and instruction type.

Instructions

Create a new Instruction associated with the specified Project. Use this to create a new Daily Log records in Procore. Creates a new Daily Log records and returns the created object on success (HTTP 201). Required parameters: project_id, title, status, instruction_type_id. Procore API: Project Management > Daily Log. Endpoint: POST /rest/v1.0/projects/{project_id}/instructions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
numberNoJSON request body field — the Number of the Instruction
titleYesJSON request body field — the Title of the Instruction
statusYesJSON request body field — the Status of the Instruction
instruction_type_idYesJSON 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 indicate it's a write operation (readOnlyHint=false) and not destructive. Description adds HTTP 201 response and endpoint, but no additional behavioral traits like permissions or side effects.

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?

Front-loaded with purpose, but has redundant phrase 'Creates a new Daily Log records' repeated. Could be more concise without losing clarity.

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 no output schema and complex input (16 params, nested objects), description is minimal. Does not explain return structure or provide guidance on nested objects. Leaves gaps for agent.

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 is 3. Description only lists required parameters, adding no new meaning beyond schema. Baseline score 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?

Clearly states the verb 'create' and resource 'Instruction', and specifies association with Project and Daily Log. Distinguishes from sibling tools like create_instruction_types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context to use for creating Daily Log records, but does not give when-not-to-use or alternatives among many sibling tools. Lacks explicit exclusions.

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