Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Project Action Plan Template Reference

create_project_action_plan_template_reference

Create a project action plan template reference in Procore to attach documents, drawings, or other items to a template item. Specify type and payload to link the reference.

Instructions

Creates a new project action plan template reference in the specified Procore project. Pass the record's fields as top-level arguments — they are nested under "plan_template_reference" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted. Creates the project action plan template reference and returns it with its new id (HTTP 201); calling it again creates another record. 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, plan_template_item_id, type, payload. Procore API: Project Management > Action Plans. Endpoint: POST /rest/v1.0/projects/{project_id}/action_plans/plan_template_references

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesJSON request body field — action Plan Reference Type
payloadYesJSON request body field — one of attachment, drawing_revision_id, file_version_id, specification_section_id, generic_tool_item_id, form_id, image_id, meeting_id, or observation_item_id is accepted depending on the type prov...
project_idYesURL path parameter — unique identifier for the project.
plan_template_item_idYesJSON request body field — project Action Plan Template Item ID
Behavior5/5

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

The description adds significant behavioral context beyond annotations: non-idempotency (calling again creates another record), HTTP 201 response with new id, error payload details (401/403/404), and project_id defaulting. These disclosures are valuable and consistent with the annotations.

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

Conciseness5/5

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

The 5 sentences are packed with specific information: creation scope, argument nesting, default behavior, idempotency, response/errors, required parameters, and API endpoint. Every sentence earns its place with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite lacking an output schema, the description covers input semantics, defaulting, response format, error statuses, and API location, making it self-sufficient. The schema and annotations handle the rest, making this complete for an agent to invoke confidently.

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 covers all 4 parameters at 100% with descriptions and an enum for type. The description enriches this by explaining that fields are passed as top-level arguments and automatically nested under 'plan_template_reference', and that project_id defaults from config. This goes beyond the schema.

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 creates a new project action plan template reference, using the specific verb 'Creates'. It distinguishes itself from sibling list/show/delete tools and company-level creation by explicitly specifying 'project' and 'new'.

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?

Context is clear: it creates a single project-scoped reference, and project_id can default from procore_set_config. However, it does not explicitly mention alternatives like bulk_create_action_plan_template_references or create_company_action_plan_template_reference, but the 'project' scope is stated.

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